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=41771>. 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=41771 ------- Additional Comments From [EMAIL PROTECTED] 2007-03-07 12:20 ------- (In reply to comment #7) > Thanks for your answer, Ruediger. As you ask, there is one balancer member > running on the same box as the webserver. So I currently assume that the sockets in CLOSE_WAIT state belong to the balancer member on your box. If httpd is not able to sent the full contents to the client it closes the connection to the backend to 1. Avoid any hickups with stuck content when reusing this connection. 2. To give the backend a chance to discover that the content requested will not be consumed and thus possible expensive operations to generate the remaining part of the content can be stopped. So I assume that the application in your balancer has not closed its part of the socket after httpd has closed its side of the socket. Can you please cross check? -- 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]
