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 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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Out of curiosity I activated the connectionTimeout in my ajp connector and my catalina.out file gets spammed with hundreds 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: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached I guess, it is because of definition of debug=9 in the same Connector. What would be a reasonable debug level? Zero? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255808:132335]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Marcus Franke [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 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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Out of curiosity I activated the connectionTimeout in my ajp connector and my catalina.out file gets spammed with hundreds 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: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached I guess, it is because of definition of debug=9 in the same Connector. What would be a reasonable debug level? Zero? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 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. Allistair. -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 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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Out of curiosity I activated the connectionTimeout in my ajp connector and my catalina.out file gets spammed with hundreds 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: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached I guess, it is because of definition of debug=9 in the same Connector. What would be a reasonable debug level? Zero? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLACK Disclaimer: The information contained within this e-mail is confidential and may be privileged. This email is intended solely for the named recipient only; if you are not authorised you must not disclose, copy, distribute, or retain this message or any part of it. If you have received this message in error please contact the sender at once so that we may take the appropriate action and avoid troubling you further. Any views expressed in this message are those of the individual sender. QAS Limited has the right lawfully to record, monitor and inspect messages between its employees and any third party. Your messages shall be subject to such lawful supervision as QAS Limited deems to be necessary in order to protect its information, its interests and its reputation. Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS Limited cannot guarantee that attachments are virus free or compatible with your systems and does not accept any liability in respect of viruses or computer problems experienced. /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255811:132338]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Allistair 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 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. Allistair. -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 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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Out of curiosity I activated the connectionTimeout in my ajp connector and my catalina.out file gets spammed with hundreds 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: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached I guess, it is because of definition of debug=9 in the same Connector. What would be a reasonable debug level? Zero? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLACK Disclaimer: The information contained within this e-mail is confidential and may be privileged. This email is intended solely for the named recipient only; if you are not authorised you must not disclose, copy, distribute, or retain this message or any part of it. If you have received this message in error please contact the sender at once so that we may take the appropriate action and avoid troubling you further. Any views expressed in this message are those of the individual sender. QAS Limited has the right lawfully to record, monitor and inspect messages between its employees and any third party. Your messages shall be subject to such lawful supervision as QAS Limited deems to be necessary in order to protect its information, its interests and its reputation. Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS Limited cannot guarantee that attachments are virus free or compatible with your systems and does not accept any liability in respect of viruses or computer problems experienced. /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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, 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 issue. I'll give them a try. Hmm, I guess its not only an issue of the mod_jk, as I restarted the apache server and still had sessions in the jk connector with an age of over 19 hours. Or am I missing something? Marcus -- Live long and prosper. -- Spock, Amok Time, stardate 3372.7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255820:132350]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Marcus Franke [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, 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 issue. I'll give them a try. Hmm, I guess its not only an issue of the mod_jk, as I restarted the apache server and still had sessions in the jk connector with an age of over 19 hours. Or am I missing something? Marcus -- Live long and prosper. -- Spock, Amok Time, stardate 3372.7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Zero. 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 connectionTimeout=2 protocol=AJP/1.3 / I tried to modify the logger definition in the server.xml using verbosity=0 !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt verbosity=0 timestamp=true/ 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? Thanks, Marcus -- 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]
Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255825:132355]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Marcus Franke [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, 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 Zero. 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 connectionTimeout=2 protocol=AJP/1.3 / I tried to modify the logger definition in the server.xml using verbosity=0 !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt verbosity=0 timestamp=true/ 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? Thanks, Marcus -- 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] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 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); -Rick -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 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 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 Zero. 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 connectionTimeout=2 protocol=AJP/1.3 / I tried to modify the logger definition in the server.xml using verbosity=0 !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt verbosity=0 timestamp=true/ 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? Thanks, Marcus -- 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]
RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached [255831:132361]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Rick [EMAIL 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 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); -Rick -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 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 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 Zero. 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 connectionTimeout=2 protocol=AJP/1.3 / I tried to modify the logger definition in the server.xml using verbosity=0 !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt verbosity=0 timestamp=true/ 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? Thanks, Marcus -- 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] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 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]
RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Thanks, Rick -Original Message- From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED] Posted At: Thursday, October 06, 2005 6:36 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 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
I`m using Tomcat 5.0.30 / Apache 2.0.54 / JK 1.2.14.1 I looked a bit in the source of the Tomcat JK connector, and the 'connectionTimeout' parameter of the Connector is relayed to 'soTimeout' of the listening JK sockets ChannelSocket.java. ...which takes us to the java.net.Socket api and SO_TIMEOUT parameter. Seems to me that mod_jk in Apache keeps the connection opened, therefore never closing it and reusing it for future calls. If so, and if I set a connectionTimeout on the Tomcat JK connector, it would always close the connection with a TimeoutException. That would explain the log entries. I don't know, I'm just guessing because my system is not in production yet, but if I set my Tomcat connector to 'no timeout' and my Apache worker to socket_timeout=30 secs, wouldn't the sockets be recycled on both ends anyway when not active for 30 secs? My Apache workers.properties looks like: worker.tomcat1.port=8009 worker.tomcat1.host=localhost worker.tomcat1.type=ajp13 worker.tomcat1.cachesize=150 worker.tomcat1.cache_timeout=600 worker.tomcat1.recycle_timeout=300 worker.tomcat1.socket_timeout=30 worker.tomcat1.socket_keepalive=1 and I haven't had the log entry in Tomcat since I 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-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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Thanks, Rick -Original Message- From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED] Posted At: Thursday, October 06, 2005 6:36 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 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
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 issue. I'll give them a try. Thanks again, 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 using Tomcat 5.0.30 / Apache 2.0.54 / JK 1.2.14.1 I looked a bit in the source of the Tomcat JK connector, and the 'connectionTimeout' parameter of the Connector is relayed to 'soTimeout' of the listening JK sockets ChannelSocket.java. ...which takes us to the java.net.Socket api and SO_TIMEOUT parameter. Seems to me that mod_jk in Apache keeps the connection opened, therefore never closing it and reusing it for future calls. If so, and if I set a connectionTimeout on the Tomcat JK connector, it would always close the connection with a TimeoutException. That would explain the log entries. I don't know, I'm just guessing because my system is not in production yet, but if I set my Tomcat connector to 'no timeout' and my Apache worker to socket_timeout=30 secs, wouldn't the sockets be recycled on both ends anyway when not active for 30 secs? My Apache workers.properties looks like: worker.tomcat1.port=8009 worker.tomcat1.host=localhost worker.tomcat1.type=ajp13 worker.tomcat1.cachesize=150 worker.tomcat1.cache_timeout=600 worker.tomcat1.recycle_timeout=300 worker.tomcat1.socket_timeout=30 worker.tomcat1.socket_keepalive=1 and I haven't had the log entry in Tomcat since I 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-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 use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Thanks, Rick -Original Message- From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED] Posted At: Thursday, October 06, 2005 6:36 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 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] - 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]
