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=36385>. 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=36385 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-02 13:08 ------- Comments inline. (In reply to comment #5) > Sending cping/cpong makes no sense if connect was successful, > and it was deliberately removed from recent versions. > ajp_connect_to_enpoint uses timeout (socket_timeout), and > if it succeeds there is no need to try sending cping/cpong. > Tomcat will either hang or simply refuse the connection if > the max thread limit gets reached, so the first phase in that > case will fail. I've found this behaviour (which I consider a bug) when Enhydra/Tomcat had a problem that allowed me to establish connections to the AJP port but wouldn't respond to any requests (including the first one on a fresh connection). > IMO there is no point of sending cping/cpong if new connection > is established. It makes sense only with already connected sockets where > it is used to deal with broken sockets. But that's the sole reason for the existence of the connect_timeout property: for sending a cping/cpong after a new connection is established. What I think that is a bug is the fact that if I use only prepost_timeout and not connect_timeout, there is no cping/cpong before the first request (at least, if this is the intended behavior, a remark should be make in the documentation). -- 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]
