tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request
Date Fri, 02 Sep 2005 11:54:11 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=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 hgomez@apache.org  2005-09-02 13:54 -------
(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 didn't agree. Even if you connect to the remote Tomcat, this one could be
hang and that was the ping/pong goal, detect a zombie or hanged tomcat.

I got case where the tomcat was able to do the accept but was in serious trouble
at a later time, and didn't process the request.

> 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.



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


Mime
View raw message