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 16357] - "connection timeout reached" in logs when using apache/jk
Date Tue, 17 Jun 2003 13:33:55 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16357>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16357

"connection timeout reached" in logs when using apache/jk





------- Additional Comments From Stefan.Kuehnel@frontis.com  2003-06-17 13:33 -------
For me the "connection timeout reached" messages only make sense together with
the "Accepted socket ...." messages which are already at debug level, where I
think they both belong.  Setting the level to WARN is only a rather ugly
workaround, because it disables for example the useful message on which
address:port this socket is listening.

BTW, the "Port busy ... " message while searching for a free port should
probably be demoted to debug level as well.

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