Hi Marcus,
  About that log entry that doesn't seem to be caught by the default
java.util.logging, I was wondering if it's a bug in the code per my original
post, noted below..  On all calls to log, isn't it required to do a check
for that log level before making the call... i.e.  isDebugEnabled(),
isInfoEnabled(), etc.   Maybe for some reason, log4j with filter without the
check? (speculation), if this is the case.. The below mentioned change may
fix the problem, I don't have the tomcat build environment setup or I would
try it.. Anyone else do their own tomcat builds that could try it quick?

> > '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"); 


-----Original Message-----
From: Marcus Franke [mailto:[EMAIL PROTECTED] 
Posted At: Friday, October 07, 2005 10:07 AM
Posted To: Tomcat Dev
Conversation: [5.5.9] Excessive jk INFO log msgs "connection timeout
Subject: Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

On Fri, Oct 07, 2005 at 05:24:27PM +0100, Allistair Crossley wrote:
> Hi,
> looks like jk is using commons logging, you'll have better success using a
log4j or commons-logging properties configuration to set the threshold to
ERROR. you may be able to do that in jk's config files too, i am sure there
is an error level setting. check out the jk docs.

Hello Allistair,

Ok, did not understand a word :)
Seems to be too late.

I now changed the debug value in the Connector now step by step down to
But no changes, the catalina.out file still fills with those timeout Infos.

    <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" 
               enableLookups="false" redirectPort="8443" debug="0"
               minProcessors="50" maxProcessors="500"
               protocol="AJP/1.3" />

I tried to modify the logger definition in the server.xml using

      <!-- Global logger unless overridden at lower levels -->
      <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="catalina_log." suffix=".txt" verbosity="0"

But its just the catalina_log and not the catalina.out which according to
the start scripts of the tomcat daemon is a redirection of stdout of the
daemon itself into the logfile.

Is there an option to make the tomcat daemon less noisy?



History tends to exaggerate.
                -- Col. Green, "The Savage Curtain", stardate 5906.4

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to