On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote:
Jean-Marc,
Actually, without the connectionTimeout set, jk seems to hold on to its
connections indefinitely and after a while, the apache to tomcat connection
hangs (pages quit serving). Could you tell me which combo of versions you
[EMAIL PROTECTED]
Received: 10/7/2005 5:20 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote:
Jean-Marc,
Actually, without the connectionTimeout set, jk seems
.
-Original Message-
From: Marcus Franke [mailto:[EMAIL PROTECTED]
Sent: 07 October 2005 17:22
To: Tomcat Users List
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout
reached
On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote:
Jean-Marc,
Actually, without
Crossley [EMAIL PROTECTED]
Received: 10/7/2005 5:23 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
Hi,
looks like jk is using commons logging, you'll have better success using a
log4j or commons-logging properties
On Thu, Oct 06, 2005 at 09:40:38AM -0700, Rick wrote:
Thanks Jean-Marc,
After checking over my workers.properties, orginally configured by someone
else, it appears to be missing some of the connection timeout handling
properties you have listed in yours. I'm guessing this is the root of my
[EMAIL PROTECTED]
Received: 10/7/2005 5:39 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Thu, Oct 06, 2005 at 09:40:38AM -0700, Rick wrote:
Thanks Jean-Marc,
After checking over my workers.properties
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
[EMAIL PROTECTED]
Received: 10/7/2005 6:05 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
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
]
Posted At: Friday, October 07, 2005 10:07 AM
Posted To: Tomcat Dev
Conversation: [5.5.9] Excessive jk INFO log msgs connection timeout
reached
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
PROTECTED]
Received: 10/7/2005 6:35 PM
To: 'Tomcat Users List' tomcat-user@jakarta.apache.org
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
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
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]
jk INFO log msgs connection timeout
reached
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
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
set the
cache and timeouts in Apache.
Hope it helps...
Jean-Marc
-Original Message-
From: Rick [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 09:54
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout
reached
Jean
-Original Message-
From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED]
Posted At: Thursday, October 06, 2005 9:15 AM
Posted To: Tomcat Dev
Conversation: [5.5.9] Excessive jk INFO log msgs connection timeout
reached
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
I`m
14 matches
Mail list logo
