I am using a Jersey StreamingOutput
that was working just fine until we upgraded to Jersey 2.16. Here's the thing. My StreamingOuput
produces output very slowly in some circumstances. I do write data regularly, but I write it pretty slowly and just a little of it at a time. I call flush()
on the OutputStream
passed to StreamingOutput.write()
every time I write any bytes, but the flush() appears to have no effect. Nothing is sent over the wire until 8K has been written to the OutputStream
. Unfortunately, in some circumstances, by the time 8K has been written, the client has timed out.
I downloaded some of the jersey source and through some debugging, I see that the OutputStream
passed to write()
is an UnCloseableOutputStream
which wraps a CommittingOutputStream
.
The CommittingOutputStream
has buffering enabled, and therefore the flush() is essentially a no-op until the response is committed (complete).
So, I am in a pickle. How can I use a StreamingOutput
(or otherwise write directly to an output stream) and force it to send bytes over the wire before the entire response is complete? Is there some other way to do this with Jersey? I can't find any methods on the ResponseBuilder
to do this. I can't find any way to turn off buffering.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…