httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41771] - Erro with mod_proxy_ajp or mod_prox_balancer
Date Tue, 13 Mar 2007 20:52:44 GMT
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 rpluem@apache.org  2007-03-13 13:52 -------
Ok, as the sockets being in CLOSE_WAIT state belong to httpd processes, my
theory seems to be wrong :-).
Another approach: I do not know the application server to which you connect via
ajp. Possibly it has a timeout for these ajp connections and closes them after a
certain idle period or it closes them for any other reason. The socket will
remain in CLOSE_WAIT status on httpd side until the connection is chosen again
from the connection pool by the specific worker. httpd will notice that the
connection has been closed by the other end, will close its end of the
connection and create a new socket for a new connection.

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message