connection timeout reached JK IsapiRedirect.dll

2005-10-12 Thread Reynir Hubner
org.apache.jk.common.ChannelSocket processConnection - - INFO: connection timeout reached Can anyone explaine these (still coming after the update). this is the config for the connector : Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=275

Re: connection timeout reached JK IsapiRedirect.dll

2005-10-12 Thread Reynir Hubner
messages into the log(stderr.log): - 12.10.2005 09:50:53 org.apache.jk.common.ChannelSocket processConnection - INFO: connection timeout reached Can anyone explaine these (still coming after the update). this is the config for the connector : Connector className=org.apache.coyote.tomcat4

Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-07 Thread Marcus Franke
of these: 07.10.2005 17:47:15 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:17 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO

Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255808:132335]

2005-10-07 Thread RTE - Meridian Club
[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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-07 Thread Allistair Crossley
. -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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255811:132338]

2005-10-07 Thread RTE - Meridian Club
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

Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-07 Thread Marcus Franke
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

Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255820:132350]

2005-10-07 Thread RTE - Meridian Club
[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

Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-07 Thread Marcus Franke
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

Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255825:132355]

2005-10-07 Thread RTE - Meridian Club
[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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-07 Thread Rick
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); -Rick -Original Message- From: Marcus Franke [mailto:[EMAIL PROTECTED

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255831:132361]

2005-10-07 Thread RTE - Meridian Club
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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-06 Thread Jean-Marc Marchand
] 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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-06 Thread Rick
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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-06 Thread Jean-Marc Marchand
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

RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-06 Thread Rick
-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

[5.5.9] Excessive jk INFO log msgs connection timeout reached

2005-10-05 Thread Rick
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

RE: INFO: connection Timeout reached

2004-11-08 Thread Varley, Roger
I've just upgraded to 4.1.31 and I'm getting org.apache.jk.common.ChannelSocket processConnection INFO: connection Timeout received messages at the console every second or so. Everything seems to be working OK so do I need to do anything about these messages? If this is normal

INFO: connection Timeout reached

2004-11-04 Thread Varley, Roger
Hi I've just upgraded to 4.1.31 and I'm getting org.apache.jk.common.ChannelSocket processConnection INFO: connection Timeout received messages at the console every second or so. Everything seems to be working OK so do I need to do anything about these messages? If this is normal behaviour, is

Re: org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

2004-04-21 Thread Bill Barker
org.apache.jk.server.JkCoyoteHandler action INFO: RESET Apr 20, 2004 11:05:14 AM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached What does this mean ?? I have the following entries in my server.xml. Connector className=org.apache.coyote.tomcat4.CoyoteConnector

org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

2004-04-20 Thread Kommineni, Sateesh \(GE Consumer Industrial\)
INFO: RESET Apr 20, 2004 11:05:14 AM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached What does this mean ?? I have the following entries in my server.xml. Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=10

Re: org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

2004-04-20 Thread Thomas Tang
processConnection INFO: connection timeout reached Hi All, I am trying to deploy a Web Application in my Tomcat and got the following Error in the Log Files.. Apr 20, 2004 11:05:04 AM org.apache.jk.server.JkCoyoteHandler action INFO: RESET

Re: [INFO] ChannelSocket - -connection timeout reached

2004-02-03 Thread Bill Barker
PROTECTED] Hi I am running the RH linux with apache and mod_jk2. On the window machine I have tomcat. When I run the examples I see this message in the windows console where tomcat is running. [INFO] ChannelSocket - -connection timeout reached Do I need to increase the time in server.xml or jk2

[INFO] ChannelSocket - -connection timeout reached

2004-02-02 Thread Asif Chowdhary
Hi I am running the RH linux with apache and mod_jk2. On the window machine I have tomcat. When I run the examples I see this message in the windows console where tomcat is running. [INFO] ChannelSocket - -connection timeout reached Do I need to increase the time in server.xml or jk2

connection timeout reached

2003-12-05 Thread L.Karam
What is the reason of this INFO to happen? 05/12/2003 06:46:01 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached It appears with sufficient frequency. What I must make to stop it? Tks Leandro Karam

jk connection timeout reached

2003-01-17 Thread Nick Wesselman
I'm seeing a lot of messages like this in my catalina.out with TC 4.1.18. Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

connection timeout reached

2003-01-16 Thread Nick Wesselman
I'm seeing a lot of messages like this in my catalina.out with TC 4.1.18. Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached