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
mturk@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From mturk@apache.org 2005-09-02 12:40 -------
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.
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
|