DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14059>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14059 HTP Response does not respond correctly to flush() ------- Additional Comments From [EMAIL PROTECTED] 2002-10-31 18:36 ------- I went back and checked the response times and behavior of the browser test. On 4.1.12 It looks like the OK data string comes back almost immediately, but the session does not release for a consistant 6.012 seconds - every time. On 4.0.6 Again the OK data string comes back immediately, the session release times are all over the map. .1 seconds to 5.01 seconds. But never the 6 seconds to match the sleep on the server. I also looked at the protocol n the wire and hereis what I see: 4.1.12 GET ... ----> HTTP/1.1 200 OK <---- Continuation <---- Continuation <---- (data frame contains "OK") 4.0.6 GET ... ----> HTTP/1.1 200 OK <---- Continuation <---- (data frame contains "OK") Continuation <---- It appears that the OK in the continuation frame indicates when the server actually closes the stream. if that is true, the TC4.1.12 close() is the operation that is not really occuring at the lines in the code. I am going to try reading the response in my client without buffering, but I'm not sure what will happen if I close the client stream, when the server still has it open. -j.p. -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
