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


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |normal
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From [EMAIL PROTECTED]  2004-11-30 21:47 -------
ChannelSocket, like most of the rest of Tomcat and its connectors, uses commons-
logging.  To get rid of this message by modifying your logging configuration, 
raise the logging level for org.apache.jk (or just the class, or another 
package as you see fit) to ERROR, FATAL, or NONE.  See the Tomcat documentation 
on logging for both 5.0 and 5.5 for examples of how to do this.

But of course, simply removing the message from your logs is only part of the 
solution.  You should configure your server and/or your network configuration 
so that these timeouts don't occur in the first place.  For help on how to do 
this, please go to the tomcat-user mailing list.

Either way, it's not a bug per-se, and since Bugzilla is not an adequate 
discussion forum (the mailing lists are the place for that), I'm closing this 
item.

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

Reply via email to