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=35292>. 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=35292 ------- Additional Comments From [EMAIL PROTECTED] 2005-06-12 13:46 ------- I don't see how that implementation actually fixes the problem. Or am I missing something fundamental? The *problem* is that the server is not reading enough bytes from the socket to eat up the TCP window and prevent an RST from allowing the client to see the response. Just changing the timeouts makes no difference, the solution needs to actually increase the number of read() calls made (and/or increase the buffer size passed to read). In the situation which lingering close is helping, the first read call is *not* going to time out; the TCP receive buffer for this socket on the server will already be non-empty so it will necessarily return data immediately. Changing that first timeout just introduces a new problem; if the client disappears completely after reading the response, the server will now hang around for thirty seconds waiting for a FIN that will never arrive, rather than just for two seconds. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
