DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=17014>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=17014 ServletResponse.flushBuffer() no longer commits the response [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-09-24 22:44 ------- I just ran into this problem myself. I've been working on integrating my own socket factory into the coyote connecter code (a socket factory that produces secure sockets) and this socket factory produces sockets that do not flush on close so I never get any replies. I don't think that socket.close() can be assumed to flush the output stream (at least the javadoc doesn't say so) and shutdownOutput() or flush() are never called. I think that this line in org.apache.coyote.http11.Http11Protocol: // recycle kernel sockets ASAP try { if (socket != null) socket.close (); } should be changed to either include a call to socket.shutdownOutput() or out.flush() before the close. /Sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
