Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-users] detecting closed connections in handlers

I'm finding that in order for handlers to detect closed connections, 
an IOException is thrown only after second flush to the response output 
stream (so, for example, after calling HttpServletResponse.flushBuffer 
to commit the response, then writing application output and flushing 
again -- exception occurs on the latter).

Is this behavior correct? why wouldn't the first flush cause the exception
to be raised?

(same behavior with 7.4.2 and 8.0M3)

thanks!



Back to the top