I got rid of this message when I realized that my AJP connector's configuration (in server.xml) had a "connectionTimeout" set. Try setting it bigger or simply removing it, which will default to 'no timeout'.
Cheers, Jean-Marc > -----Original Message----- > From: Rick [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 05, 2005 18:19 > To: 'Tomcat Users List' > Subject: [5.5.9] Excessive jk INFO log msgs "connection > timeout reached" > > > Anyone know the proper way to handle these messages? I get > piles of them in > catalina.out > > ------------ > Oct 5, 2005 3:00:23 PM org.apache.jk.common.ChannelSocket > processConnection > INFO: connection timeout reached > ------------ > > Tried adding the following line to the default > <catalina_home>/common/classes/logging.properties > org.apache.jk.common.ChannelSocket.level=WARN > > Has no effect. The only thing I have been able to find is > people using > Log4j instead of the default java.util.logging that came > setup with Tomcat > 5.5. Was wondering, is that the only way? If so, why does > it work w/ Log4j > and not the default java.util.logging? > > Looking at the source for > 'org.apache.jk.common.ChannelSocket', the line > reads... > > log.info( "connection timeout reached"); > > Should it not instead read... > > if(log.isInfoEnabled()) log.info( "connection timeout reached"); > > > Anyway, thanks for any help to this. > > -Rick Gavin > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
