Howdy, >You said: >OTOH - After the startup message - nothing really should be written to >it >without making an effort to do so. So only badly written code which uses >System.out/err will be the victim. > >Here's an example of what apx. 70% of my catalina.out file contains: >5189887 [Thread-14] INFO common.ChannelSocket - connection timeout >reached >5201847 [Thread-10] INFO common.ChannelSocket - connection timeout >reached >5216537 [Thread-8] INFO common.ChannelSocket - connection timeout >reached >5228577 [Thread-14] INFO common.ChannelSocket - connection timeout >reached >5228677 [Thread-10] INFO common.ChannelSocket - connection timeout >reached >5236557 [Thread-28] INFO common.ChannelSocket - connection timeout >reached
As the messages themselves say, they're INFO-level, not a warning or error. You can disable these by adding a commons-logging configuration file to tomcat. >and on , and on with the occasional 'broken pipe' stack trace. I guess >the jk connector is badly coded ? I wouldn't say it's badly coded. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
