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 28905] New: - ChannelSocket fills stdout log with "connection timeout reached"
Date Tue, 11 May 2004 17:26:56 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=28905>.
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=28905

ChannelSocket fills stdout log with "connection timeout reached"

           Summary: ChannelSocket fills stdout log with "connection timeout
                    reached"
           Product: Tomcat 5
           Version: 5.0.24
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:AJP
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: George.Lindholm@ubc.ca


My stdout log file keeps filling up with:

May 11, 2004 5:33:21 AM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached

They may be useful while debugging, but in a production environment these
messages just hide real problems logged to stdout.

Apache 2.0.49.

   George

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