connection timeout reached JK IsapiRedirect.dll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm using tomcat 4.1.x and Coyote JK connector, with IIS 5. I just updated to isapi_redirect-1.2.14.dll. I did that because I've been getting alot of those error 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.CoyoteConnector port=8009 minProcessors=5 maxProcessors=275 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=1 useURIValidationHack=false tomcatAuthentication=true protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ thanx, [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDTN9K19KgIQihNwgRAlEpAJ9sNvVp9B5cVaOROkswt2A0oyZu7ACfVDCA PE2yIFPgurN3CX0jPv2duHo= =pm9R -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: connection timeout reached JK IsapiRedirect.dll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ah sorry, I mean IIS 6 (the newest one). - -reynir Reynir Hubner wrote: Hi, I'm using tomcat 4.1.x and Coyote JK connector, with IIS 5. I just updated to isapi_redirect-1.2.14.dll. I did that because I've been getting alot of those error 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.CoyoteConnector port=8009 minProcessors=5 maxProcessors=275 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=1 useURIValidationHack=false tomcatAuthentication=true protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ thanx, [EMAIL PROTECTED] - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDTOFG19KgIQihNwgRAtBdAJ9Tzd03Xisk0cmCIzmXN3ijGICvKwCaA/Hw ZmGsSQ7Sv2iijXswfVLhHV4= =dnj5 -END PGP SIGNATURE- - 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 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]
Tomcat behind IIS - Session timeout is ignored
Hello list, I have a problem with a tomcat 5.0.28 installation connected to IIS 6.0 (Windows 2003 server) with isapi_redirect.dll Everything is working well, except for the session timeout. The timeout is set to 60 minutes in the context's web.xml file (session-timeout60/session-timeout) which works great in many other installations (without IIS, though) As far as I could tell, the sessions are purely managed by tomcat, so IIS should not pose a problem, but still... Can anyone shed some light on this? Thanks, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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: Session timeout issues
On 15/09/05, Leon Rosenberg [EMAIL PROTECTED] wrote: Hi, I don't know if this fits, but could it be, that your problem is related to the tomcat session synchronization bug? http://issues.apache.org/bugzilla/show_bug.cgi?id=36541 That does look like a potential issue. However, I think I may have tracked this down to cookies and switching between HTTP and HTTPS. There are two scenarios: 1) User starts at an HTTP page and is given a cookie. This cookie can be used in secure and non secure requests. 2) User starts at an HTTPS page and is given a cookie. This cookie is only valid for secure requests (because it has Set-Cookie: ;Secure in the response header). When a user is redirected to an HTTP page they are given a *new* cookie and a new HttpSession is created on the server. Can you tell me the exact semantics of the secure attribute on the connector element? The documentation just says Set this attribute to true if you wish to have calls to request.isSecure() to return true for requests received Thanks James Shaw On 9/15/05, James Shaw [EMAIL PROTECTED] wrote: On 14/09/05, James Shaw [EMAIL PROTECTED] wrote: I have two issues relating to sessions: 1) Sessions seem to be expired too soon. This happens very infrequently for me (perhaps 1 in 1000 requests). I'm adding some HttpSessionListeners and HttpSessionAttributeListeners to attempt to locate this problem, but have little to go on at the moment. I have some more info on this problem. During the login process, the original JSESSIONID that tomcat gives to the browser is being lost and a new HttpSession with a new id is being created. So either the browser is not sending the cookie containing the session id, or Tomcat is somehow losing the id. Does anyone have an idea what this problem could be? Perhaps you could point me to some information about how Tomcat receives cookies and maps these to their respective HttpSession objects. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session timeout issues
On 14/09/05, James Shaw [EMAIL PROTECTED] wrote: I have two issues relating to sessions: 1) Sessions seem to be expired too soon. This happens very infrequently for me (perhaps 1 in 1000 requests). I'm adding some HttpSessionListeners and HttpSessionAttributeListeners to attempt to locate this problem, but have little to go on at the moment. I have some more info on this problem. During the login process, the original JSESSIONID that tomcat gives to the browser is being lost and a new HttpSession with a new id is being created. So either the browser is not sending the cookie containing the session id, or Tomcat is somehow losing the id. Does anyone have an idea what this problem could be? Perhaps you could point me to some information about how Tomcat receives cookies and maps these to their respective HttpSession objects. Thanks James Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Session timeout issues
I have two issues relating to sessions: 1) Sessions seem to be expired too soon. This happens very infrequently for me (perhaps 1 in 1000 requests). I'm adding some HttpSessionListeners and HttpSessionAttributeListeners to attempt to locate this problem, but have little to go on at the moment. 2) Session objects are being expired too late. Some session objects are persisting for far longer than the 30 minutes I've specified in web.xml. I've checked this with an HttpSessionListener today, for example: Timestamp: Wed Sep 14 12:26:21 BST 2005 ID:C945C8BC10E58E3947A5475C001DBA35 Last Accessed: Wed Sep 14 11:35:43 BST 2005 Backtrace: at presentation.listener.DebugSessionListener.sessionDestroyed(DebugSessionListener.java:54) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:675) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:567) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:655) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:640) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1283) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1568) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1557) at java.lang.Thread.run(Unknown Source) I realise that this isn't enough information to really diagnose the problem but I'm hoping that you may be able to give me some suggestions for what to do next. Thanks in advance James Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Page timeout displaying database rows
Env: Linux: Apache 1.3.33 Tomcat 4.1.30 MySql 4.1.10 There is a page member_list.jsp which displays a grid of members. After 20/75 members are displayed, html is displayed: a class=CobaltDataLink href=MemberMaint.jsp?fMemberID=83s_fStatusName=Activetype=notLoggedr et_link=%2FtmJ%2Fme This page was working! - it seems to be an Apache/Tomcat config issue Any tips on where to look? Setting connectionTimeout=0 removes the message from Catalina.out, but the page still does not display correctly. !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
session timeout problems
Hello, within my web application i defined a session timeout of 30 minutes. But some sessions strangly survive this timeout and keep being valid until an explicit call to invalidate(). I already implemented a HttpSessionListener to keep track of session creation, destruction, lastAccessedTime and MaxInactiveInterval. So i recieve a HttpSessionEvent for every session being created or destroyed. I recognized that i never got a call to sessionDestroyed(HttpSessionEvent) for those strange timeout survivers. I am quite lost and have no idea how to solve this situation. Any suggestions ? Greets, Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: timeout, but not session
On Fri, Jul 29, 2005 at 12:15:13PM -0400, joelsherriff wrote: : We've got a servlet problem that we're trying to track down. The problem : causes one of the threads to spin. What kind of thread is this, user-managed (i.e. you created it yourself) or container-managed (Tomcat keeping track of servlets and such)? : Until we can solve the problem, : can anyone suggest anything that can timeout these out-of-control threads? : Session timeouts timeout on inactivity, correct? I don't know if that : will work in this case...but I might try it anyway. Let's take a step back: specifically, what are the symptoms of the problem? What do you mean by out of control? -and how is the are the threads being allocated/defined? -QM -- software -- http://www.brandxdev.net/ tech news -- http://www.RoarNetworX.com/ code scan -- http://www.JxRef.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
timeout, but not session
We've got a servlet problem that we're trying to track down. The problem causes one of the threads to spin. Until we can solve the problem, can anyone suggest anything that can timeout these out-of-control threads? Session timeouts timeout on inactivity, correct? I don't know if that will work in this case...but I might try it anyway.
How do you set the session timeout in tomcat so that the session only timeouts when the browser is closed?
How do you set the session timeout in tomcat so that the session only timeouts when the browser is closed? This e mail is from DLA Piper Rudnick Gray Cary UK LLP. The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this email is received in error, please contact DLA Piper Rudnick Gray Cary UK LLP on +44 (0) 8700 11 quoting the name of the sender and the email address to which it has been sent and then delete it. Please note that neither DLA Piper Rudnick Gray Cary UK LLP nor the sender accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. DLA Piper Rudnick Gray Cary UK LLP is a limited liability partnership registered in England and Wales (registered number OC307847) which provides services from offices in England, Belgium, Germany and the People's Republic of China. A list of members is open for inspection at its registered office and principal place of business 3 Noble Street, London EC2V 7EE. Partner denotes member of a limited liability partnership. DLA Piper Rudnick Gray Cary UK LLP is regulated by the Law Society and is a member of DLA Piper Rudnick Gray Cary, a global legal services organisation, the members of which are separate and distinct legal entities. For further information, please refer to www.dlapiper.com.
RE: How do you set the session timeout in tomcat so that the session only timeouts when the browser is closed?
From: Harland, David [mailto:[EMAIL PROTECTED] How do you set the session timeout in tomcat so that the session only timeouts when the browser is closed? You don't. There is no way in any Web architecture of reliably detecting whether a browser has closed, or whether it has merely disconnected from the server for now and will be reconnecting later. This is a generic problem with any stateful browser-based application and is not specific to Tomcat. - Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do you set the session timeout in tomcat so that the session only timeouts when the browser is closed?
On 6/7/05, Harland, David [EMAIL PROTECTED] wrote: How do you set the session timeout in tomcat so that the session only timeouts when the browser is closed? Possible solution may be to refresh the page frequently and set a short interval for session time out. You might use a frame for this. If you use the AJAX approach to develop web applications it will be easy. I hadnt seen GMail session expired. -- rgds Anto Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat totally ignores my timeout-settings
Hi everybody, I have the following problem: I have created and registered an HttpSessionListener which sets the MaxInactiveInterval to 120 seconds in the sessionCreated-method, whenever a new session is created. Then I have System.out.println(session is killed) in the sessionDestroyed-method of this listener. But the sessionDestroyed-method is never called and the session is NEVER killed. I have also a session-config session-timeout2/session-timeout /session-config in my web.xml but this doesn't help ether. What am I doing wrong? Why doesn't tomcat kill my session, why does it ignore my settings? The following is a small part from my logfile. As you can see, the timeout is never called by tomcat (look at the time-values). The session is only destroyed if the user uses the logout-button: ## /var/log/messages/tomcat5/ catalina.out ### new session-object created, # '9A8DC55C6B8043AA6BE12E9027699C64' - CreationTime (DD.MM.YY HH:MM): 18.05.05 14:11 - MaxInactiveInterval: 120 seconds - Web-Browser: Mozilla/5.0 (compatible; Konqueror/3.4; Linux 2.6.11-gentoo-r8; X11; i686; de) KHTML/3.4.0 (like Gecko) logged in: admin (Administrator, 11)', from session-id '9A8DC55C6B8043AA6BE12E9027699C64' - Time (DD.MM.YY HH:MM): 18.05.05 14:15 admin (Administrator, 9A8DC55C6B8043AA6BE12E9027699C64) manually logs out! - Time (DD.MM.YY HH:MM): 18.05.05 14:20 session destroyed for 9A8DC55C6B8043AA6BE12E9027699C64 (username: admin) What can I do to solve this problem? Greetings, Hendrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat totally ignores my timeout-settings
Are you creating a basic authentication or form based authentication ? -Original Message- From: Hendrik Neumann [mailto:[EMAIL PROTECTED] Sent: 18 May 2005 14:11 To: tomcat-user@jakarta.apache.org Subject: Tomcat totally ignores my timeout-settings Hi everybody, I have the following problem: I have created and registered an HttpSessionListener which sets the MaxInactiveInterval to 120 seconds in the sessionCreated-method, whenever a new session is created. Then I have System.out.println(session is killed) in the sessionDestroyed-method of this listener. But the sessionDestroyed-method is never called and the session is NEVER killed. I have also a session-config session-timeout2/session-timeout /session-config in my web.xml but this doesn't help ether. What am I doing wrong? Why doesn't tomcat kill my session, why does it ignore my settings? The following is a small part from my logfile. As you can see, the timeout is never called by tomcat (look at the time-values). The session is only destroyed if the user uses the logout-button: ## /var/log/messages/tomcat5/ catalina.out ### new session-object created, # '9A8DC55C6B8043AA6BE12E9027699C64' - CreationTime (DD.MM.YY HH:MM): 18.05.05 14:11 - MaxInactiveInterval: 120 seconds - Web-Browser: Mozilla/5.0 (compatible; Konqueror/3.4; Linux 2.6.11-gentoo-r8; X11; i686; de) KHTML/3.4.0 (like Gecko) logged in: admin (Administrator, 11)', from session-id '9A8DC55C6B8043AA6BE12E9027699C64' - Time (DD.MM.YY HH:MM): 18.05.05 14:15 admin (Administrator, 9A8DC55C6B8043AA6BE12E9027699C64) manually logs out! - Time (DD.MM.YY HH:MM): 18.05.05 14:20 session destroyed for 9A8DC55C6B8043AA6BE12E9027699C64 (username: admin) What can I do to solve this problem? Greetings, Hendrik - 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: Tomcat totally ignores my timeout-settings
nor, still now I don't use an offical authentication-method which is protected by a login-config-tag. my login-method just loads a usergroup out of the database which has specific access-rights and associates it with the current user-objects which belongs to one session-object. but this runs without tomcat or the web.xml-file or any offical auth-method. I'm quite sure that the timeout-problems are independent from my login-method. I have a personal testing-server which has just been used by myself in the last 8 hours and till now the tomcat-manager tells me, that there are 35 sessions running (because the sessions are not killed)... P.S: I'm using a hibernate-connection-pool, could this cause the trouble? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat totally ignores my timeout-settings
okay, now I've created a new, small web-project with a very simple web.xml just containing the HttpSessionListener, a 2-minute-session-timeout and very small index.jsp and it works without any problems! but my original jsf-web-app still doesn not release the sessions (I already have 40 sessions on my personal testing systems)... So is it a bug in my web-app? And if it is - how can I get to the bottom of this problem, how can I solve it? Any ideas??? Am Mittwoch, 18. Mai 2005 15:11 schrieb Hendrik Neumann: Hi everybody, I have the following problem: I have created and registered an HttpSessionListener which sets the MaxInactiveInterval to 120 seconds in the sessionCreated-method, whenever a new session is created. Then I have System.out.println(session is killed) in the sessionDestroyed-method of this listener. But the sessionDestroyed-method is never called and the session is NEVER killed. I have also a session-config session-timeout2/session-timeout /session-config in my web.xml but this doesn't help ether. What am I doing wrong? Why doesn't tomcat kill my session, why does it ignore my settings? The following is a small part from my logfile. As you can see, the timeout is never called by tomcat (look at the time-values). The session is only destroyed if the user uses the logout-button: ## /var/log/messages/tomcat5/ catalina.out ### new session-object created, # '9A8DC55C6B8043AA6BE12E9027699C64' - CreationTime (DD.MM.YY HH:MM): 18.05.05 14:11 - MaxInactiveInterval: 120 seconds - Web-Browser: Mozilla/5.0 (compatible; Konqueror/3.4; Linux 2.6.11-gentoo-r8; X11; i686; de) KHTML/3.4.0 (like Gecko) logged in: admin (Administrator, 11)', from session-id '9A8DC55C6B8043AA6BE12E9027699C64' - Time (DD.MM.YY HH:MM): 18.05.05 14:15 admin (Administrator, 9A8DC55C6B8043AA6BE12E9027699C64) manually logs out! - Time (DD.MM.YY HH:MM): 18.05.05 14:20 session destroyed for 9A8DC55C6B8043AA6BE12E9027699C64 (username: admin) What can I do to solve this problem? Greetings, Hendrik - 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]
delete temporary content after session timeout
Hi, I have an app that uploads user files in a temporary folder. I want to delete them when the session ends. I know I could solve this with a cron-job, but I'm looking for a way to solve it with Tomcat. Does anyone have an idea how to solve it? Thx for your help in advance, cheers, Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: delete temporary content after session timeout
Write a SessionListener... it has two methods, one that fires when a session is created, one when it is destroyed. That should do the trick for you. That's not a Tomcat-specific solution either, so it should be rather portable should you ever need to move to another app server. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com Bob Wobbler wrote: Hi, I have an app that uploads user files in a temporary folder. I want to delete them when the session ends. I know I could solve this with a cron-job, but I'm looking for a way to solve it with Tomcat. Does anyone have an idea how to solve it? Thx for your help in advance, cheers, Robert - 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: delete temporary content after session timeout
that sounds very useful, not something I've done before -- can I ask a few questions - 1) how does one bind that into Tomcat -- declare a session listener in (I presume) web.xml? 2) as I'm using Spring Framework, is this still relevant (or is there a spring-specific way of binding in a session listener --- sorry, ought to ask that on a spring list...) 3) can you recommend the best reference material / sites on managing sessions (standard tomcat docs seem to have nothing on sessions I can find.) Tim Frank W. Zammetti wrote: Write a SessionListener... it has two methods, one that fires when a session is created, one when it is destroyed. That should do the trick for you. That's not a Tomcat-specific solution either, so it should be rather portable should you ever need to move to another app server. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: delete temporary content after session timeout
Let's see...
(1) You are correct, it's nothing more than an entry in web.xml.
Remember, this isn't a Tomcat-specific thing, it's a J2EE thing (servlet
spec specifically I think), so it's YOUR APP'S web.xml. The entry is
simply:
listener
listener-classcom.company.app.MySessionListener/listener-class
/listener
Assuming that class is available to the classloader, your all set.
(2) I'm not too familiar with the Spring framework, but since it's still
built on top of the servlet spec, this would apply just the same, it
should be independant of app server and framework in use. Spring may
have it's own mechanism for doing this, but given the choice I'd chose
the standard approach, which is a listener.
(3) I don't have any good references handy, but just Googling
SessionListener will turn up plenty of hits. Just to save you some
time, here's the basic structure of a SessionListener class:
package com.company.app.MySessionListener
import javax.servlet.http.HttpSession;
import javax.servlet.http.HttpSessionEvent;
public class MySessionListener implements HttpSessionListener {
/**
* This method is called by the servlet container just after http
session is
* created.
*
* @param bevent/b HttpSessionEvent
*/
public void sessionCreated(HttpSessionEvent event) {
}
/**
* This method is called by the servlet container just before http
session is
* destroyed.
*
* @param bevent/b HttpSessionEvent
*/
public void sessionDestroyed(HttpSessionEvent event) {
}
}
Couldn't be simpler! You can do event.getSession() in both if you need
to do anything with the session (like, for the OP, if you have a
reference to the user ID who's directory you want to purge of temporary
files).
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
Tim Diggins wrote:
that sounds very useful, not something I've done before -- can I ask a
few questions -
1) how does one bind that into Tomcat -- declare a session listener in
(I presume) web.xml?
2) as I'm using Spring Framework, is this still relevant (or is there a
spring-specific way of binding in a session listener --- sorry, ought to
ask that on a spring list...)
3) can you recommend the best reference material / sites on managing
sessions (standard tomcat docs seem to have nothing on sessions I can
find.)
Tim
Frank W. Zammetti wrote:
Write a SessionListener... it has two methods, one that fires when a
session is created, one when it is destroyed. That should do the
trick for you. That's not a Tomcat-specific solution either, so it
should be rather portable should you ever need to move to another app
server.
-
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]
[OT] Session beans: testing for timeout and avoiding null pointer exceptions
I have a some java beans in the session scope which are instantiated by one page by get their properties updated by several other pages. When the session expires Tomcat (correctly) throws an error when it tries to update the no longer existing bean. My question is thus: how do I detect its state and redirects users to the page re-initializing the bean? /Thomas FONT SIZE=1 FACE=Arial___ Vi goer opmaerksom paa, at denne e-mail kan indeholde fortrolig information. Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge svar-funktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller kopiere den. Selv om e-mailen og ethvert vedhaeftet bilag efter vores overbevisning er fri for virus og andre fejl, som kan paavirke computeren eller it-systemet, hvori den modtages og laeses, aabnes den paa modtagerens eget ansvar. Vi paatager os ikke noget ansvar for tab og skade, som er opstaaet i forbindelse med at modtage og bruge e-mailen. ___ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message. /FONT
wil Tomcat stop request thread after a timeout?
Hello, I wonder if Tomcat will stop a servlet execution thread after a certain timeout (adjustable?)? Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
session-timeout
Hi every, from web.xml: session-config session-timeout30/session-timeout /session-config Does the session-timeout refer to an idle session or an active session ? Thk in advance Cedric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session-timeout
If more than idle for 30 minutes. -Tim Cédric Buschini wrote: Hi every, from web.xml: session-config session-timeout30/session-timeout /session-config Does the session-timeout refer to an idle session or an active session ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session-timeout
Think of the timeout as a 30 minute countdown timer. Every time there is any session activity, like a page request, the timers starts over. If the timer ever gets to 0, then the session times out. Jay Vertical Technology Group http://www.vtgroup.com/ -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Thursday, April 14, 2005 10:13 AM To: Tomcat Users List Subject: Re: session-timeout If more than idle for 30 minutes. -Tim Cédric Buschini wrote: Hi every, from web.xml: session-config session-timeout30/session-timeout /session-config Does the session-timeout refer to an idle session or an active session ? - 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: session-timeout
thank you !! Jay Burgess wrote: Think of the timeout as a 30 minute countdown timer. Every time there is any session activity, like a page request, the timers starts over. If the timer ever gets to 0, then the session times out. Jay Vertical Technology Group http://www.vtgroup.com/ -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Thursday, April 14, 2005 10:13 AM To: Tomcat Users List Subject: Re: session-timeout If more than idle for 30 minutes. -Tim Cédric Buschini wrote: Hi every, from web.xml: session-config session-timeout30/session-timeout /session-config Does the session-timeout refer to an idle session or an active session ? - 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]
Re: Way to specify SingleSignOn session timeout?
After looking at the code, it looks like the SSO session doesn't go away until all other sessions for the user have expired. So, as far as I can tell, the SSO session doesn't have it's own session timeout as far as I can tell. Jon - Original Message - From: Jonathan Eric Miller [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, April 13, 2005 11:00 AM Subject: Re: Way to specify SingleSignOn session timeout? Thanks, but, I know how to set it for a given application. I want to know how to set it or at least find out what the default value is for the global session. I've noticed that there are two cookies. One is JSESSIONID which is for the application session. The other is JSESSIONSSO is is presumably for the global session. Jon - Original Message - From: Peter Rossbach [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Tuesday, April 12, 2005 10:56 PM Subject: Re: Way to specify SingleSignOn session timeout? Look inside conf/web.xml !-- created sessions by modifying the value -- session-config session-timeout30/session-timeout /session-config Peter Jonathan Eric Miller schrieb: I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know what the default session timeout is set to? Is there a way to specify this timeout? I'm finding that sometimes my session will timeout within an application, but, it doesn't redisplay the login page. I want to try to set it up so that the session timeout period is the same for all my applications (and the same for the global one) and that whenever the session times out, the login page is displayed. Jon - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Way to specify SingleSignOn session timeout?
After looking at the code, it looks like the SSO session doesn't go away until all other sessions for the user have expired. So, as far as I can tell, the SSO session doesn't have it's own session timeout as far as I can tell. Jon - Original Message - From: Jonathan Eric Miller [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, April 13, 2005 11:00 AM Subject: Re: Way to specify SingleSignOn session timeout? Thanks, but, I know how to set it for a given application. I want to know how to set it or at least find out what the default value is for the global session. I've noticed that there are two cookies. One is JSESSIONID which is for the application session. The other is JSESSIONSSO is is presumably for the global session. Jon - Original Message - From: Peter Rossbach [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Tuesday, April 12, 2005 10:56 PM Subject: Re: Way to specify SingleSignOn session timeout? Look inside conf/web.xml !-- created sessions by modifying the value -- session-config session-timeout30/session-timeout /session-config Peter Jonathan Eric Miller schrieb: I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know what the default session timeout is set to? Is there a way to specify this timeout? I'm finding that sometimes my session will timeout within an application, but, it doesn't redisplay the login page. I want to try to set it up so that the session timeout period is the same for all my applications (and the same for the global one) and that whenever the session times out, the login page is displayed. Jon - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Way to specify SingleSignOn session timeout?
On 4/14/05, Jonathan Eric Miller [EMAIL PROTECTED] wrote: After looking at the code, it looks like the SSO session doesn't go away until all other sessions for the user have expired. So, as far as I can tell, the SSO session doesn't have it's own session timeout as far as I can tell. Indeed. OTOH, if one of the sessions is explicitely invalidated, the SSO will go away right away. I think that's the most appropriate behavior, but changing it is very easy using a little code hacking. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Way to specify SingleSignOn session timeout?
Thanks, but, I know how to set it for a given application. I want to know how to set it or at least find out what the default value is for the global session. I've noticed that there are two cookies. One is JSESSIONID which is for the application session. The other is JSESSIONSSO is is presumably for the global session. Jon - Original Message - From: Peter Rossbach [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Tuesday, April 12, 2005 10:56 PM Subject: Re: Way to specify SingleSignOn session timeout? Look inside conf/web.xml !-- created sessions by modifying the value -- session-config session-timeout30/session-timeout /session-config Peter Jonathan Eric Miller schrieb: I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know what the default session timeout is set to? Is there a way to specify this timeout? I'm finding that sometimes my session will timeout within an application, but, it doesn't redisplay the login page. I want to try to set it up so that the session timeout period is the same for all my applications (and the same for the global one) and that whenever the session times out, the login page is displayed. Jon - 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]
Running code on session timeout
Hey, I have been looking all over for a way to run code on a session time out. Basically, before a session times out, I need to perform some functionality on the data in that session. Ive read about Session Manager and Session Listeners, but I have not been able to find any examples of how these work. Is it possible to do what I am asking, and if so, does anyone know of a good reference site? Thanks - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running code on session timeout
Java Server Pages, 3rd Edition, O'Reilly - great book. I can send you an example later tonight. - Original Message - From: Chris Bender [EMAIL PROTECTED] Date: Wednesday, April 13, 2005 10:26 am Subject: Running code on session timeout Hey, I have been looking all over for a way to run code on a session time out. Basically, before a session times out, I need to perform some functionality on the data in that session. Ive read about Session Manager and Session Listeners, but I have not been able to find any examples of how these work. Is it possible to do what I am asking, and if so, does anyone know of a good reference site? Thanks --- -- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. --- -- 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]
Thread Timeout
Is there a way to set the timeout on request processing threads? I'd like to be able to say that If a request takes more than 60 seconds, then kill it. Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Way to specify SingleSignOn session timeout?
I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know what the default session timeout is set to? Is there a way to specify this timeout? I'm finding that sometimes my session will timeout within an application, but, it doesn't redisplay the login page. I want to try to set it up so that the session timeout period is the same for all my applications (and the same for the global one) and that whenever the session times out, the login page is displayed. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Way to specify SingleSignOn session timeout?
Look inside conf/web.xml !-- created sessions by modifying the value below. -- session-config session-timeout30/session-timeout /session-config Peter Jonathan Eric Miller schrieb: I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know what the default session timeout is set to? Is there a way to specify this timeout? I'm finding that sometimes my session will timeout within an application, but, it doesn't redisplay the login page. I want to try to set it up so that the session timeout period is the same for all my applications (and the same for the global one) and that whenever the session times out, the login page is displayed. Jon - 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]
Unlimited session timeout
Hi,
I need in some exceptionnal condition to disable the session timeout for
one request.
Is there some convenient way to do so?
My idea is to do this but I'm unsure :
In the exceptionnal servlet (at the beginning):
session.setAttribute(OLD_TIMEOUT, new
Integer(session.getMaxInactiveInterval()));
session.setMaxInactiveInterval(-1);
In my filter:
Integer oldTimeout = (Integer) session.getAttribute(OLD_TIMEOUT);
if(oldTimeout != null) {
session.setMaxInactiveInterval(oldTimeout.intValue());
}
What do you think about this method is it safe/working?
Maybe there is a way to do it with session listeners (by cancelling the
call to invalidate, I don't know if it is possible).
Thank you.
David.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unlimited session timeout
you can set timeout from Tomcat Admin = Connections.
--- David Causse [EMAIL PROTECTED] wrote:
Hi,
I need in some exceptionnal condition to disable the
session timeout for
one request.
Is there some convenient way to do so?
My idea is to do this but I'm unsure :
In the exceptionnal servlet (at the beginning):
session.setAttribute(OLD_TIMEOUT, new
Integer(session.getMaxInactiveInterval()));
session.setMaxInactiveInterval(-1);
In my filter:
Integer oldTimeout = (Integer)
session.getAttribute(OLD_TIMEOUT);
if(oldTimeout != null) {
session.setMaxInactiveInterval(oldTimeout.intValue());
}
What do you think about this method is it
safe/working?
Maybe there is a way to do it with session listeners
(by cancelling the
call to invalidate, I don't know if it is possible).
Thank you.
David.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-Ted
__
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unlimited session timeout
It is not my problem. I need to change it for only one servlet.
Thanks.
fed fin wrote:
you can set timeout from Tomcat Admin = Connections.
--- David Causse [EMAIL PROTECTED] wrote:
Hi,
I need in some exceptionnal condition to disable the
session timeout for
one request.
Is there some convenient way to do so?
My idea is to do this but I'm unsure :
In the exceptionnal servlet (at the beginning):
session.setAttribute(OLD_TIMEOUT, new
Integer(session.getMaxInactiveInterval()));
session.setMaxInactiveInterval(-1);
In my filter:
Integer oldTimeout = (Integer)
session.getAttribute(OLD_TIMEOUT);
if(oldTimeout != null) {
session.setMaxInactiveInterval(oldTimeout.intValue());
}
What do you think about this method is it
safe/working?
Maybe there is a way to do it with session listeners
(by cancelling the
call to invalidate, I don't know if it is possible).
Thank you.
David.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-Ted
__
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Edit session timeout
Hello! How to edit session timeout? Tomcat's default value is 30mins... 30 minutes of inactivity then a session will expire... In my apps, i think 30minutes is too long.. i want 5 minutes of inactivity before session expires... is it in server.xml? i only see connectionTimeout which is 2? is connectionTimeout the same with sessionTimeout? Thanks and regards, Aris mailto:[EMAIL PROTECTED]
Re: Edit session timeout
From: Aris Javier [EMAIL PROTECTED] How to edit session timeout? Tomcat's default value is 30mins... Look in web.xml instead of server.xml. You can change it for the entire container, or on a per-webapp basis, depending on which web.xml you edit. (Works for Tomcat 4.1, I haven't moved to 5 yet...) -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Edit session timeout
I looked at my web.xml, and no sessionTimeout found there... can you give me an example on how to write it down in web.xml? thanks! aris -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:25 PM To: Tomcat Users List Subject: Re: Edit session timeout From: Aris Javier [EMAIL PROTECTED] How to edit session timeout? Tomcat's default value is 30mins... Look in web.xml instead of server.xml. You can change it for the entire container, or on a per-webapp basis, depending on which web.xml you edit. (Works for Tomcat 4.1, I haven't moved to 5 yet...) -- Wendy Smoak - 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: Edit session timeout
From: Aris Javier [mailto:[EMAIL PROTECTED] Subject: RE: Edit session timeout I looked at my web.xml, and no sessionTimeout found there... can you give me an example on how to write it down in web.xml? Not sure what you meant by my web.xml, since, as Wendy noted, there's a global one in the conf directory, as well as one in the WEB-INF directory of each web app. The session timeout is usually in the global one, but can be overridden in each web app if needed. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Edit session timeout
session-config session-timeout120/session-timeout /session-config Look, at the web.xml file inside the conf directory, the global web.xml file that is. You can usually find this right above the mime-type mapping definitions. Drew. On Sun, 2005-01-30 at 20:28, Aris Javier wrote: I looked at my web.xml, and no sessionTimeout found there... can you give me an example on how to write it down in web.xml? thanks! aris -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:25 PM To: Tomcat Users List Subject: Re: Edit session timeout From: Aris Javier [EMAIL PROTECTED] How to edit session timeout? Tomcat's default value is 30mins... Look in web.xml instead of server.xml. You can change it for the entire container, or on a per-webapp basis, depending on which web.xml you edit. (Works for Tomcat 4.1, I haven't moved to 5 yet...) -- Wendy Smoak - 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]
RE: Edit session timeout
Thanks Drew! I found it.. =) can I also use this setting per web app? by editing web.xml per web app? -Original Message- From: Drew Jorgenson [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:41 PM To: Tomcat Users List Subject: RE: Edit session timeout session-config session-timeout120/session-timeout /session-config Look, at the web.xml file inside the conf directory, the global web.xml file that is. You can usually find this right above the mime-type mapping definitions. Drew. On Sun, 2005-01-30 at 20:28, Aris Javier wrote: I looked at my web.xml, and no sessionTimeout found there... can you give me an example on how to write it down in web.xml? thanks! aris -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:25 PM To: Tomcat Users List Subject: Re: Edit session timeout From: Aris Javier [EMAIL PROTECTED] How to edit session timeout? Tomcat's default value is 30mins... Look in web.xml instead of server.xml. You can change it for the entire container, or on a per-webapp basis, depending on which web.xml you edit. (Works for Tomcat 4.1, I haven't moved to 5 yet...) -- Wendy Smoak - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Edit session timeout
Yes. Doug - Original Message - From: Aris Javier [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Sunday, January 30, 2005 11:53 PM Subject: RE: Edit session timeout Thanks Drew! I found it.. =) can I also use this setting per web app? by editing web.xml per web app? -Original Message- From: Drew Jorgenson [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:41 PM To: Tomcat Users List Subject: RE: Edit session timeout session-config session-timeout120/session-timeout /session-config Look, at the web.xml file inside the conf directory, the global web.xml file that is. You can usually find this right above the mime-type mapping definitions. Drew. On Sun, 2005-01-30 at 20:28, Aris Javier wrote: I looked at my web.xml, and no sessionTimeout found there... can you give me an example on how to write it down in web.xml? thanks! aris -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:25 PM To: Tomcat Users List Subject: Re: Edit session timeout From: Aris Javier [EMAIL PROTECTED] How to edit session timeout? Tomcat's default value is 30mins... Look in web.xml instead of server.xml. You can change it for the entire container, or on a per-webapp basis, depending on which web.xml you edit. (Works for Tomcat 4.1, I haven't moved to 5 yet...) -- Wendy Smoak - 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] - 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: Edit session timeout
Thanks Everybody! =) -Original Message- From: Parsons Technical Services [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:56 PM To: Tomcat Users List Subject: Re: Edit session timeout Yes. Doug - Original Message - From: Aris Javier [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Sunday, January 30, 2005 11:53 PM Subject: RE: Edit session timeout Thanks Drew! I found it.. =) can I also use this setting per web app? by editing web.xml per web app? -Original Message- From: Drew Jorgenson [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:41 PM To: Tomcat Users List Subject: RE: Edit session timeout session-config session-timeout120/session-timeout /session-config Look, at the web.xml file inside the conf directory, the global web.xml file that is. You can usually find this right above the mime-type mapping definitions. Drew. On Sun, 2005-01-30 at 20:28, Aris Javier wrote: I looked at my web.xml, and no sessionTimeout found there... can you give me an example on how to write it down in web.xml? thanks! aris -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 12:25 PM To: Tomcat Users List Subject: Re: Edit session timeout From: Aris Javier [EMAIL PROTECTED] How to edit session timeout? Tomcat's default value is 30mins... Look in web.xml instead of server.xml. You can change it for the entire container, or on a per-webapp basis, depending on which web.xml you edit. (Works for Tomcat 4.1, I haven't moved to 5 yet...) -- Wendy Smoak - 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] - 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]
Re: timeout when reading 401 response [was: persistent HTTP 1.1 connections with Tomcat 5.5.4?]
It looks like the timeout is occurring when the first response is being read, so this changes the problem. I'm receiving a 401 Unauthorized response with the following headers: Server: Apache-Coyote/1.1 WWW-Authenticate: [...] Content-Type: text/html;charset=utf-8 Content-Length: 952 Date: Thu, 06 Jan 2005 19:47:43 GMT I try to read the 952 bytes, and that's when I get the 15-second hang before a timeout. The response is generated on the server with: response.sendError(401); Where are those 952 bytes, and why can't I read them, I wonder? Garret Garret Wilson wrote: Does Tomcat 5.5.4 support HTTP 1.1 persistent connections? I'm connecting to a Tomcat servlet from a custom Java client, and the first request/response goes fine: socketAddress=new InetSocketAddress(host, port); channel=SocketChannel.open(socketAddress); inputStream=new BufferedInputStream(newInputStream(channel)); outputStream=new BufferedOutputStream(newOutputStream(channel)); The response headers do *not* have a Connection: close header, which means the connection should stay open. The response is a 401 Unauthorized, so I place credentials in the request and send it again to the same output stream. Then I try to read another response from the same input stream. My program hangs until the connection times out. What the matter with persistent connections here? Thanks, Garret - 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: timeout when reading 401 response [was: persistent HTTP 1.1 connections with Tomcat 5.5.4?]
So this is getting stranger. Just to preclude any error on my part, I did a simple loop that output every character received from the response. The HTTP response status line and headers come down fine, including the CRLF that separates the headers from the body. And then---timeout after 15 seconds. But the strange part is that if I connect using Firefox, I can view the entire response---an HTML document including the 401 status code. This document length is---you guessed it---952 bytes long, just like the Content-Length header says. Why can't I read the body from Java, yet Firefox can read it? Is there a bug with Channels.newInputStream()? Garret Garret Wilson wrote: It looks like the timeout is occurring when the first response is being read, so this changes the problem. I'm receiving a 401 Unauthorized response with the following headers: Server: Apache-Coyote/1.1 WWW-Authenticate: [...] Content-Type: text/html;charset=utf-8 Content-Length: 952 Date: Thu, 06 Jan 2005 19:47:43 GMT I try to read the 952 bytes, and that's when I get the 15-second hang before a timeout. The response is generated on the server with: response.sendError(401); Where are those 952 bytes, and why can't I read them, I wonder? Garret Garret Wilson wrote: Does Tomcat 5.5.4 support HTTP 1.1 persistent connections? I'm connecting to a Tomcat servlet from a custom Java client, and the first request/response goes fine: socketAddress=new InetSocketAddress(host, port); channel=SocketChannel.open(socketAddress); inputStream=new BufferedInputStream(newInputStream(channel)); outputStream=new BufferedOutputStream(newOutputStream(channel)); The response headers do *not* have a Connection: close header, which means the connection should stay open. The response is a 401 Unauthorized, so I place credentials in the request and send it again to the same output stream. Then I try to read another response from the same input stream. My program hangs until the connection times out. What the matter with persistent connections here? Thanks, Garret - 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]
Re: timeout when reading 401 response [was: persistent HTTP 1.1 connectionswith Tomcat 5.5.4?]
Garret Wilson wrote: So this is getting stranger. Just to preclude any error on my part, I did a simple loop that output every character received from the response. The HTTP response status line and headers come down fine, including the CRLF that separates the headers from the body. And then---timeout after 15 seconds. But the strange part is that if I connect using Firefox, I can view the entire response---an HTML document including the 401 status code. This document length is---you guessed it---952 bytes long, just like the Content-Length header says. Why can't I read the body from Java, yet Firefox can read it? Is there a bug with Channels.newInputStream()? Garret Garret Wilson wrote: It looks like the timeout is occurring when the first response is being read, so this changes the problem. I'm receiving a 401 Unauthorized response with the following headers: Server: Apache-Coyote/1.1 WWW-Authenticate: [...] Content-Type: text/html;charset=utf-8 Content-Length: 952 Date: Thu, 06 Jan 2005 19:47:43 GMT I try to read the 952 bytes, and that's when I get the 15-second hang before a timeout. The response is generated on the server with: response.sendError(401); Where are those 952 bytes, and why can't I read them, I wonder? Garret Garret Wilson wrote: Does Tomcat 5.5.4 support HTTP 1.1 persistent connections? I'm connecting to a Tomcat servlet from a custom Java client, and the first request/response goes fine: socketAddress=new InetSocketAddress(host, port); channel=SocketChannel.open(socketAddress); inputStream=new BufferedInputStream(newInputStream(channel)); outputStream=new BufferedOutputStream(newOutputStream(channel)); The response headers do *not* have a Connection: close header, which means the connection should stay open. The response is a 401 Unauthorized, so I place credentials in the request and send it again to the same output stream. Then I try to read another response from the same input stream. My program hangs until the connection times out. What the matter with persistent connections here? Thanks, Garret Actually what is happening is this You are using a buffered stream. It is reading past the amount returnedand then the tcp/ip socket is blocking because you have it open as a keep alive. You have to only read the number of bytes available and not keep trying to squeeze the blood out of the turnip... ;-) I'll almost bet you money that is what is happening. Try to not use a buffered input stream and see what you get. If I'm wrong I'm wrong let me know. Hope it works. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: timeout when reading 401 response [was: persistent HTTP 1.1 connectionswith Tomcat 5.5.4?]
Wade Chandler wrote: Garret Wilson wrote: So this is getting stranger. Just to preclude any error on my part, I did a simple loop that output every character received from the response. The HTTP response status line and headers come down fine, including the CRLF that separates the headers from the body. And then---timeout after 15 seconds. But the strange part is that if I connect using Firefox, I can view the entire response---an HTML document including the 401 status code. This document length is---you guessed it---952 bytes long, just like the Content-Length header says. Why can't I read the body from Java, yet Firefox can read it? Is there a bug with Channels.newInputStream()? Garret Garret Wilson wrote: It looks like the timeout is occurring when the first response is being read, so this changes the problem. I'm receiving a 401 Unauthorized response with the following headers: Server: Apache-Coyote/1.1 WWW-Authenticate: [...] Content-Type: text/html;charset=utf-8 Content-Length: 952 Date: Thu, 06 Jan 2005 19:47:43 GMT I try to read the 952 bytes, and that's when I get the 15-second hang before a timeout. The response is generated on the server with: response.sendError(401); Where are those 952 bytes, and why can't I read them, I wonder? Garret Garret Wilson wrote: Does Tomcat 5.5.4 support HTTP 1.1 persistent connections? I'm connecting to a Tomcat servlet from a custom Java client, and the first request/response goes fine: socketAddress=new InetSocketAddress(host, port); channel=SocketChannel.open(socketAddress); inputStream=new BufferedInputStream(newInputStream(channel)); outputStream=new BufferedOutputStream(newOutputStream(channel)); The response headers do *not* have a Connection: close header, which means the connection should stay open. The response is a 401 Unauthorized, so I place credentials in the request and send it again to the same output stream. Then I try to read another response from the same input stream. My program hangs until the connection times out. What the matter with persistent connections here? Thanks, Garret Actually what is happening is this You are using a buffered stream. It is reading past the amount returnedand then the tcp/ip socket is blocking because you have it open as a keep alive. You have to only read the number of bytes available and not keep trying to squeeze the blood out of the turnip... ;-) I'll almost bet you money that is what is happening. Try to not use a buffered input stream and see what you get. If I'm wrong I'm wrong let me know. Hope it works. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] See the read method of the SocketChannel...as I'm sure it will be getting called by the InputStream wrapper from the object. Don't think about trying to make the SocketChannel so that isBlocking returns false either because if all the data isn't there and it isn't blocking and the buffer doesn't have any data (at that exact moment you make a call) it will return as if it had read all of the data and then you'd be messed up that way to. I'm writing this all assuming you are using keep alives. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: timeout when reading 401 response [was: persistent HTTP 1.1 connectionswith Tomcat 5.5.4?]
Wade Chandler wrote: Wade Chandler wrote: Garret Wilson wrote: So this is getting stranger. Just to preclude any error on my part, I did a simple loop that output every character received from the response. The HTTP response status line and headers come down fine, including the CRLF that separates the headers from the body. And then---timeout after 15 seconds. But the strange part is that if I connect using Firefox, I can view the entire response---an HTML document including the 401 status code. This document length is---you guessed it---952 bytes long, just like the Content-Length header says. Why can't I read the body from Java, yet Firefox can read it? Is there a bug with Channels.newInputStream()? Garret Garret Wilson wrote: It looks like the timeout is occurring when the first response is being read, so this changes the problem. I'm receiving a 401 Unauthorized response with the following headers: Server: Apache-Coyote/1.1 WWW-Authenticate: [...] Content-Type: text/html;charset=utf-8 Content-Length: 952 Date: Thu, 06 Jan 2005 19:47:43 GMT I try to read the 952 bytes, and that's when I get the 15-second hang before a timeout. The response is generated on the server with: response.sendError(401); Where are those 952 bytes, and why can't I read them, I wonder? Garret Garret Wilson wrote: Does Tomcat 5.5.4 support HTTP 1.1 persistent connections? I'm connecting to a Tomcat servlet from a custom Java client, and the first request/response goes fine: socketAddress=new InetSocketAddress(host, port); channel=SocketChannel.open(socketAddress); inputStream=new BufferedInputStream(newInputStream(channel)); outputStream=new BufferedOutputStream(newOutputStream(channel)); The response headers do *not* have a Connection: close header, which means the connection should stay open. The response is a 401 Unauthorized, so I place credentials in the request and send it again to the same output stream. Then I try to read another response from the same input stream. My program hangs until the connection times out. What the matter with persistent connections here? Thanks, Garret Actually what is happening is this You are using a buffered stream. It is reading past the amount returnedand then the tcp/ip socket is blocking because you have it open as a keep alive. You have to only read the number of bytes available and not keep trying to squeeze the blood out of the turnip... ;-) I'll almost bet you money that is what is happening. Try to not use a buffered input stream and see what you get. If I'm wrong I'm wrong let me know. Hope it works. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] See the read method of the SocketChannel...as I'm sure it will be getting called by the InputStream wrapper from the object. Don't think about trying to make the SocketChannel so that isBlocking returns false either because if all the data isn't there and it isn't blocking and the buffer doesn't have any data (at that exact moment you make a call) it will return as if it had read all of the data and then you'd be messed up that way to. I'm writing this all assuming you are using keep alives. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] And one more tad bit If you really need to use buffering in this case it might make sense to do that in your read loop yourself so you can control the max number of bytes read...that or make a buffered input stream which you can set the max number of bytes to read into the buffer forover all max number that is. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: solved: timeout when reading 401 response [was: persistent HTTP 1.1 connectionswith Tomcat 5.5.4?]
Wade Chandler wrote: Actually what is happening is this You are using a buffered stream. It is reading past the amount returnedand then the tcp/ip socket is blocking because you have it open as a keep alive. You have to only read the number of bytes available and not keep trying to squeeze the blood out of the turnip... ;-) I'll almost bet you money that is what is happening. Try to not use a buffered input stream and see what you get. If I'm wrong I'm wrong let me know. Hope it works. Wade, thanks so very much for responding. I was sitting here dumbfounded wondering what in the world could be happening. But you're wrong. ;) I had already thrown out the BufferedInputStream to eliminate that. I switched to straight sockets. I set up a simple loop that simply read bytes until receiving a timeout. The timeout occurred after the CRLF divider, even though the Content-Length said 952. Accessing the site from Firefox showed all the content. Puzzled? Yeah, so was I. Then I realized that in my Java client I was testing my new HTTP routines with the HEAD method! (You can start the ridicule, now...) The whole point of the HEAD method is that it doesn't send content---it simply sends a Content-Length indicating how long the content would have been. In fact, RFC 2616 says that the server MUST NOT return a message-body in the response for the HEAD method (9.4). Now, what threw me off is that the response was an error status, a 401 Unauthorized. The Content-Length is in line with the spec, returning the length of the content which would have been returned if a GET had been used. As an error was returned, however, the Content-Length was returning the length of the error message---the error message that would have been returned had a GET been used. Now, all this is technically to the letter of RFC 2616, but I wonder what would happen if a server were to send back a 405 Method Not Allowed for HEAD. There would be no way to get at the error message, because HEAD doesn't send back content. Using GET would succeed, so technically the Content-Length of HEAD in this case wouldn't be the content length of a response from GET. I'm thinking that RFC 2616 should probably have made an exception to the no content rule for HEAD when an error condition is being reported. But that's the least of my worries. I just need to tell my client to ignore all content in a response to HEAD. Oddly, though, this means that a thread can't simply pull HTTP responses down from a persistent connection without knowing to which request each response belongs---i.e. whether to trust the Content-Length or not! In any case, thanks for the input. It looks like your responses will be useful when I finally switch over to non-blocking I/O support. Garret - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: solved: timeout when reading 401 response [was: persistent HTTP1.1 connectionswith Tomcat 5.5.4?]
Garret Wilson wrote: Wade Chandler wrote: Actually what is happening is this You are using a buffered stream. It is reading past the amount returnedand then the tcp/ip socket is blocking because you have it open as a keep alive. You have to only read the number of bytes available and not keep trying to squeeze the blood out of the turnip... ;-) I'll almost bet you money that is what is happening. Try to not use a buffered input stream and see what you get. If I'm wrong I'm wrong let me know. Hope it works. Wade, thanks so very much for responding. I was sitting here dumbfounded wondering what in the world could be happening. But you're wrong. ;) I had already thrown out the BufferedInputStream to eliminate that. I switched to straight sockets. I set up a simple loop that simply read bytes until receiving a timeout. The timeout occurred after the CRLF divider, even though the Content-Length said 952. Accessing the site from Firefox showed all the content. Puzzled? Yeah, so was I. Then I realized that in my Java client I was testing my new HTTP routines with the HEAD method! (You can start the ridicule, now...) The whole point of the HEAD method is that it doesn't send content---it simply sends a Content-Length indicating how long the content would have been. In fact, RFC 2616 says that the server MUST NOT return a message-body in the response for the HEAD method (9.4). Now, what threw me off is that the response was an error status, a 401 Unauthorized. The Content-Length is in line with the spec, returning the length of the content which would have been returned if a GET had been used. As an error was returned, however, the Content-Length was returning the length of the error message---the error message that would have been returned had a GET been used. Now, all this is technically to the letter of RFC 2616, but I wonder what would happen if a server were to send back a 405 Method Not Allowed for HEAD. There would be no way to get at the error message, because HEAD doesn't send back content. Using GET would succeed, so technically the Content-Length of HEAD in this case wouldn't be the content length of a response from GET. I'm thinking that RFC 2616 should probably have made an exception to the no content rule for HEAD when an error condition is being reported. But that's the least of my worries. I just need to tell my client to ignore all content in a response to HEAD. Oddly, though, this means that a thread can't simply pull HTTP responses down from a persistent connection without knowing to which request each response belongs---i.e. whether to trust the Content-Length or not! In any case, thanks for the input. It looks like your responses will be useful when I finally switch over to non-blocking I/O support. Garret - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] lol. I won't ridiculewe all make the mistakes that make us go... (Homer Simpson)..DOH Glad you got it resolved. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Session timeout
Hi everybody, Is it possible to configure the session timeout using the org.apache.catalina.session.StandardManager Session Manager or am I forced to use the Persistent Manager just for doing so? (Tomcat v4.1) Regards, F. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session timeout
How about trying? Put this inside your web-app in web.xml session-config session-timeout10/session-timeout /session-config The number within the session-timeout element must be expressed in minutes. Works for me with the StandardManager, in tomcat 5 Trond Freddy Villalba A. wrote: Hi everybody, Is it possible to configure the session timeout using the org.apache.catalina.session.StandardManager Session Manager or am I forced to use the Persistent Manager just for doing so? (Tomcat v4.1) Regards, F. - 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]
timeout + SingleSignOn + pre-compiled JSPs
Hi, I'm using TC 5.0.28 running 3 WARs with SingleSignOn feature. I also have code that modify the user's timeout for authenticated users only. (Anonymous have 5 minutes and authenticated users have 1 hour). It has been worked for a year without problems! Recently I'm getting short (5 minutes) timeouts when changing contexts even for authenticated users...Since we haven't modified our apps, the only suspect I could identify (so far) is our deployment schema - We've just changed our deployments from exploded files to 3 WAR files with pre-compiled jsps using the Tomcat Deployer... Is there anyone with the same problem? Is it possible to get into timeout problems using WAR instead of files? Thanks in advance... Paulo Alvim Powerlogic - Brazil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: INFO: connection Timeout reached
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 there anyway I can stop Tomcat from logging these messages as it makes it impossible to see any other messages since they scroll off the console too quickly? I realise that this is probably an FAQ but I would be grateful if someone could point me in the right direction on this as I don't seem to be getting anywhere. Googling has revealed a suggestion that I should be setting the verbosity parameter on the Logger in my server.xml to suppress INFO messages, but the documentation at http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/logger.html suggests that the default out-of-the-box setting should be to display error messages only. Regards Roger __ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection Timeout
Does anyone know any way that I can tell tomcat to kill the 'thread' if it isn't back in a ready state within 30 seconds? (waiting for new requests) Thanks Andrew On 05.11.2004, at 16:20, Phillip Qin wrote: Byte recv and byte sent? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 10:18 AM To: Tomcat Users List Subject: Re: Connection Timeout Hi Phillip, The request is for example a 10K image. Regards Andrew On 05.11.2004, at 16:11, Phillip Qin wrote: My guess is the request was serviced by Tomcat, and took that much time. What did your request column tell? A huge request, file upload? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 4:24 AM To: Tomcat Users List Subject: Connection Timeout Dear List, In /manager/status, I occasionally see connections where the status is 'S' and the time column is huge! 1 ms. Does this mean that the request is still being processed by tomcat? or is this a request waiting to be picked up - ie: chunked? If so, is there any way I can set a timeout for this, as a time 10 seconds makes very little sense with our application? Thanks in advance, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session-timeout means tomcat restart
Sorry for not replying sooner, I've been busy for a few days. Can you say more about the crashing? Any evidence from the logs? A bit difficult to be any more specific without more to go on really :) However, I have references to them from the controller so that shouldn't be the problem... eh? You mention controller. Are you using TC as-is, or are you using a framework such as struts or JSF by any chance? If you suspect that the problem is triggered by a closing session, why not try shortening the session timeout to a shorter length and see if it crashes quicker? In fact, it's worth checking whether the crash is around the time of the session expiry or not. If not, then your problem may not be directly caused by TC at all.? Do you have any event listeners? If you have one for sessionDestroyed/sessionWillPassivate, what does this code do? -Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Saturday 06 November 2004 00:51 To: Steve Kirk Cc: Tomcat Users List Subject: Re: session-timeout means tomcat restart Well, this is amazingly frustrating. My TC 5.0.28 running on Linux FC2 is completely crashing about every half hr when I have a webapp open and don't interact with it. I no longer have a time-out element in my web.xml so that doesn't seem to matter. TC shutdown and restart does not work. Instead, I'm required to hard boot my machine. I'm hung just trying to access the static welcome page of any app, although I do know that init() of the webapp I'm working on is being called. Eric On Fri, 5 Nov 2004 15:43:28 -0800, Eric Wulff [EMAIL PROTECTED] wrote: Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasource connection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your servlet is simple, or if it's more complex, then perhaps better places to put them would be the servlet context, or a field of the servlet class/instance. it all depends on your particular situation. whichever you choose though, you must make sure that connections are closed (or returned to the pool) when you have finished with them. this generally involves careful use of try/catch/finally. if restarting the webapp fixes the problem, it could be that your database objects are initialised in the servlet init() method, which is then called again when the webapp restarts. but if this were the case then I'm not sure how session timeout could cause the problem that you describe. datasource connection pooling is not necessarily the answer. you can still use up all your database resources and/or leave them hanging whether you pool them or not! 2
Re: RE: session-timeout means tomcat restart
We had a 'hung, and won't work without a reboot problem' and it was two things - we had to update some driver for the intel NIC cards in our server (for RedHat ES) and had to change some settings to get better NIC throughput. Hope it helps. - Original Message - From: Steve Kirk [EMAIL PROTECTED] Date: Monday, November 8, 2004 4:19 pm Subject: RE: session-timeout means tomcat restart Sorry for not replying sooner, I've been busy for a few days. Can you say more about the crashing? Any evidence from the logs? A bit difficult to be any more specific without more to go on really :) However, I have references to them from the controller so that shouldn't be the problem... eh? You mention controller. Are you using TC as-is, or are you using a framework such as struts or JSF by any chance? If you suspect that the problem is triggered by a closing session, why not try shortening the session timeout to a shorter length and see if it crashes quicker? In fact, it's worth checking whether the crash is around the time of the session expiry or not. If not, then your problem may not be directly caused by TC at all.? Do you have any event listeners? If you have one for sessionDestroyed/sessionWillPassivate, what does this code do? -Original Message- From: Eric Wulff [EMAIL PROTECTED] Sent: Saturday 06 November 2004 00:51 To: Steve Kirk Cc: Tomcat Users List Subject: Re: session-timeout means tomcat restart Well, this is amazingly frustrating. My TC 5.0.28 running on Linux FC2 is completely crashing about every half hr when I have a webapp open and don't interact with it. I no longer have a time-out element in my web.xml so that doesn't seem to matter. TC shutdown and restart does not work. Instead, I'm required to hard boot my machine. I'm hung just trying to access the static welcome page of any app, although I do know that init() of the webapp I'm working on is being called. Eric On Fri, 5 Nov 2004 15:43:28 -0800, Eric Wulff [EMAIL PROTECTED] wrote: Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasourceconnection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your servlet is simple, or if it's more complex, then perhaps better places to put them would be the servlet context, or a field of the servlet class/instance. it all depends on your particular situation. whichever you choose though, you must make sure that connections are closed (or returned to the pool) when you have finished with them. this generally involves careful
Re: session-timeout means tomcat restart
Hi Steve, sorry for lack of details. In any case, problem solved. I am developing a webapp in the MVC style and was referring to the 'C' of the MVC when mentioning the controller. I am using TC as-is however. There was a bug in a data source validity check upon login making it so the data source was not getting re-established if need be. Then it would just hang on login. Not sure why I was often required to hard boot but it's not longer a problem since I corrected the data source hook. Eric On Mon, 8 Nov 2004 22:19:27 -, Steve Kirk [EMAIL PROTECTED] wrote: Sorry for not replying sooner, I've been busy for a few days. Can you say more about the crashing? Any evidence from the logs? A bit difficult to be any more specific without more to go on really :) However, I have references to them from the controller so that shouldn't be the problem... eh? You mention controller. Are you using TC as-is, or are you using a framework such as struts or JSF by any chance? If you suspect that the problem is triggered by a closing session, why not try shortening the session timeout to a shorter length and see if it crashes quicker? In fact, it's worth checking whether the crash is around the time of the session expiry or not. If not, then your problem may not be directly caused by TC at all.? Do you have any event listeners? If you have one for sessionDestroyed/sessionWillPassivate, what does this code do? -Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Saturday 06 November 2004 00:51 To: Steve Kirk Cc: Tomcat Users List Subject: Re: session-timeout means tomcat restart Well, this is amazingly frustrating. My TC 5.0.28 running on Linux FC2 is completely crashing about every half hr when I have a webapp open and don't interact with it. I no longer have a time-out element in my web.xml so that doesn't seem to matter. TC shutdown and restart does not work. Instead, I'm required to hard boot my machine. I'm hung just trying to access the static welcome page of any app, although I do know that init() of the webapp I'm working on is being called. Eric On Fri, 5 Nov 2004 15:43:28 -0800, Eric Wulff [EMAIL PROTECTED] wrote: Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasource connection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your servlet is simple, or if it's more complex, then perhaps better places to put them would be the servlet context, or a field of the servlet class/instance. it all depends on your particular situation. whichever you choose though, you must
RE: RE: session-timeout means tomcat restart
sorry but no. what about the other points. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday 08 November 2004 22:37 To: Tomcat Users List Subject: Re: RE: session-timeout means tomcat restart We had a 'hung, and won't work without a reboot problem' and it was two things - we had to update some driver for the intel NIC cards in our server (for RedHat ES) and had to change some settings to get better NIC throughput. Hope it helps. - Original Message - From: Steve Kirk [EMAIL PROTECTED] Date: Monday, November 8, 2004 4:19 pm Subject: RE: session-timeout means tomcat restart Sorry for not replying sooner, I've been busy for a few days. Can you say more about the crashing? Any evidence from the logs? A bit difficult to be any more specific without more to go on really :) However, I have references to them from the controller so that shouldn't be the problem... eh? You mention controller. Are you using TC as-is, or are you using a framework such as struts or JSF by any chance? If you suspect that the problem is triggered by a closing session, why not try shortening the session timeout to a shorter length and see if it crashes quicker? In fact, it's worth checking whether the crash is around the time of the session expiry or not. If not, then your problem may not be directly caused by TC at all.? Do you have any event listeners? If you have one for sessionDestroyed/sessionWillPassivate, what does this code do? -Original Message- From: Eric Wulff [EMAIL PROTECTED] Sent: Saturday 06 November 2004 00:51 To: Steve Kirk Cc: Tomcat Users List Subject: Re: session-timeout means tomcat restart Well, this is amazingly frustrating. My TC 5.0.28 running on Linux FC2 is completely crashing about every half hr when I have a webapp open and don't interact with it. I no longer have a time-out element in my web.xml so that doesn't seem to matter. TC shutdown and restart does not work. Instead, I'm required to hard boot my machine. I'm hung just trying to access the static welcome page of any app, although I do know that init() of the webapp I'm working on is being called. Eric On Fri, 5 Nov 2004 15:43:28 -0800, Eric Wulff [EMAIL PROTECTED] wrote: Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasourceconnection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your
Re: RE: session-timeout means tomcat restart
Other points? I posted details when I solved this problem, last Friday, but I only now realized that someone changed the thread, a couple have, and my post is related to that thread. Perhaps you didn't see that. If you're wondering about event listeners, I have not implemented any as of yet. If you're still looking for other points then I'll need you to be specific. Also, in looking back at this thread I noticed you were the one who suggested creating a myapp.xml and where to put it. This was the suggestion I followed that finally solved my problem. Many thx for that! I still have yet to find a mention of this in TC 5.0 docs. Eric btw, I am required to manually put that myapp.xml at CATALINA_HOME/conf/Catalina/localhost/. I tried creating a META-INF, located at /myapp/ with a context.xml, but this did not result in a dynamic copy at CATALINA_HOME/conf/Catalina/localhost/. On Tue, 9 Nov 2004 00:51:09 -, Steve Kirk [EMAIL PROTECTED] wrote: sorry but no. what about the other points. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday 08 November 2004 22:37 To: Tomcat Users List Subject: Re: RE: session-timeout means tomcat restart We had a 'hung, and won't work without a reboot problem' and it was two things - we had to update some driver for the intel NIC cards in our server (for RedHat ES) and had to change some settings to get better NIC throughput. Hope it helps. - Original Message - From: Steve Kirk [EMAIL PROTECTED] Date: Monday, November 8, 2004 4:19 pm Subject: RE: session-timeout means tomcat restart Sorry for not replying sooner, I've been busy for a few days. Can you say more about the crashing? Any evidence from the logs? A bit difficult to be any more specific without more to go on really :) However, I have references to them from the controller so that shouldn't be the problem... eh? You mention controller. Are you using TC as-is, or are you using a framework such as struts or JSF by any chance? If you suspect that the problem is triggered by a closing session, why not try shortening the session timeout to a shorter length and see if it crashes quicker? In fact, it's worth checking whether the crash is around the time of the session expiry or not. If not, then your problem may not be directly caused by TC at all.? Do you have any event listeners? If you have one for sessionDestroyed/sessionWillPassivate, what does this code do? -Original Message- From: Eric Wulff [EMAIL PROTECTED] Sent: Saturday 06 November 2004 00:51 To: Steve Kirk Cc: Tomcat Users List Subject: Re: session-timeout means tomcat restart Well, this is amazingly frustrating. My TC 5.0.28 running on Linux FC2 is completely crashing about every half hr when I have a webapp open and don't interact with it. I no longer have a time-out element in my web.xml so that doesn't seem to matter. TC shutdown and restart does not work. Instead, I'm required to hard boot my machine. I'm hung just trying to access the static welcome page of any app, although I do know that init() of the webapp I'm working on is being called. Eric On Fri, 5 Nov 2004 15:43:28 -0800, Eric Wulff [EMAIL PROTECTED] wrote: Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm
RE: Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout?
Resending...anyone know??? -Original Message- From: Dan Carwin Sent: Friday, November 05, 2004 11:01 AM To: [EMAIL PROTECTED] Subject: Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout? what is the default maxThreads in tomcat 5 jk2/coyote connector? What is the default serverTimeout ? #channelSocket.serverTimeout=??? #channelSocket.maxThreads=??? (fwiw I'm referring to the version included in tc 5.0.28) Thanks, Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection Timeout
Dear List, In /manager/status, I occasionally see connections where the status is 'S' and the time column is huge! 1 ms. Does this mean that the request is still being processed by tomcat? or is this a request waiting to be picked up - ie: chunked? If so, is there any way I can set a timeout for this, as a time 10 seconds makes very little sense with our application? Thanks in advance, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session-timeout means tomcat restart
-Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasource connection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your servlet is simple, or if it's more complex, then perhaps better places to put them would be the servlet context, or a field of the servlet class/instance. it all depends on your particular situation. whichever you choose though, you must make sure that connections are closed (or returned to the pool) when you have finished with them. this generally involves careful use of try/catch/finally. if restarting the webapp fixes the problem, it could be that your database objects are initialised in the servlet init() method, which is then called again when the webapp restarts. but if this were the case then I'm not sure how session timeout could cause the problem that you describe. datasource connection pooling is not necessarily the answer. you can still use up all your database resources and/or leave them hanging whether you pool them or not! 2. Often tomcat hangs without responding at all, to static or dynamic requests, after it's been left for an hr or more with no interaction. Might this be related to the memory leaks I hear about? you don't say which platform/ versions you are using so memory leaks are hard to comment on. IMHO the issues above are more likely to be the problem so check those first before suspecting an error in TC :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connection Timeout
My guess is the request was serviced by Tomcat, and took that much time. What did your request column tell? A huge request, file upload? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 4:24 AM To: Tomcat Users List Subject: Connection Timeout Dear List, In /manager/status, I occasionally see connections where the status is 'S' and the time column is huge! 1 ms. Does this mean that the request is still being processed by tomcat? or is this a request waiting to be picked up - ie: chunked? If so, is there any way I can set a timeout for this, as a time 10 seconds makes very little sense with our application? Thanks in advance, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:418b46a1164289526310470!
Re: Connection Timeout
Hi Phillip, The request is for example a 10K image. Regards Andrew On 05.11.2004, at 16:11, Phillip Qin wrote: My guess is the request was serviced by Tomcat, and took that much time. What did your request column tell? A huge request, file upload? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 4:24 AM To: Tomcat Users List Subject: Connection Timeout Dear List, In /manager/status, I occasionally see connections where the status is 'S' and the time column is huge! 1 ms. Does this mean that the request is still being processed by tomcat? or is this a request waiting to be picked up - ie: chunked? If so, is there any way I can set a timeout for this, as a time 10 seconds makes very little sense with our application? Thanks in advance, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:418b46a1164289526310470! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connection Timeout
Byte recv and byte sent? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 10:18 AM To: Tomcat Users List Subject: Re: Connection Timeout Hi Phillip, The request is for example a 10K image. Regards Andrew On 05.11.2004, at 16:11, Phillip Qin wrote: My guess is the request was serviced by Tomcat, and took that much time. What did your request column tell? A huge request, file upload? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 4:24 AM To: Tomcat Users List Subject: Connection Timeout Dear List, In /manager/status, I occasionally see connections where the status is 'S' and the time column is huge! 1 ms. Does this mean that the request is still being processed by tomcat? or is this a request waiting to be picked up - ie: chunked? If so, is there any way I can set a timeout for this, as a time 10 seconds makes very little sense with our application? Thanks in advance, Andrew - 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] !DSPAM:418b99c3205412059510077!
Re: Connection Timeout
Hi Phillip, S506331 ms17 KB0 KBx.x.2.24www.x.comGET /x//img/x/Image.gif HTTP/1.1 Regards Andrew On 05.11.2004, at 16:20, Phillip Qin wrote: Byte recv and byte sent? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 10:18 AM To: Tomcat Users List Subject: Re: Connection Timeout Hi Phillip, The request is for example a 10K image. Regards Andrew On 05.11.2004, at 16:11, Phillip Qin wrote: My guess is the request was serviced by Tomcat, and took that much time. What did your request column tell? A huge request, file upload? -Original Message- From: Andrew Miehs [mailto:[EMAIL PROTECTED] Sent: November 5, 2004 4:24 AM To: Tomcat Users List Subject: Connection Timeout Dear List, In /manager/status, I occasionally see connections where the status is 'S' and the time column is huge! 1 ms. Does this mean that the request is still being processed by tomcat? or is this a request waiting to be picked up - ie: chunked? If so, is there any way I can set a timeout for this, as a time 10 seconds makes very little sense with our application? Thanks in advance, Andrew - 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] !DSPAM:418b99c3205412059510077!
Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout?
what is the default maxThreads in tomcat 5 jk2/coyote connector? What is the default serverTimeout ? #channelSocket.serverTimeout=??? #channelSocket.maxThreads=??? (fwiw I'm referring to the version included in tc 5.0.28) Thanks, Dan
Re: session-timeout means tomcat restart
Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasource connection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your servlet is simple, or if it's more complex, then perhaps better places to put them would be the servlet context, or a field of the servlet class/instance. it all depends on your particular situation. whichever you choose though, you must make sure that connections are closed (or returned to the pool) when you have finished with them. this generally involves careful use of try/catch/finally. if restarting the webapp fixes the problem, it could be that your database objects are initialised in the servlet init() method, which is then called again when the webapp restarts. but if this were the case then I'm not sure how session timeout could cause the problem that you describe. datasource connection pooling is not necessarily the answer. you can still use up all your database resources and/or leave them hanging whether you pool them or not! 2. Often tomcat hangs without responding at all, to static or dynamic requests, after it's been left for an hr or more with no interaction. Might this be related to the memory leaks I hear about? you don't say which platform/ versions you are using so memory leaks are hard to comment on. IMHO the issues above are more likely to be the problem so check those first before suspecting an error in TC :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session-timeout means tomcat restart
Well, this is amazingly frustrating. My TC 5.0.28 running on Linux FC2 is completely crashing about every half hr when I have a webapp open and don't interact with it. I no longer have a time-out element in my web.xml so that doesn't seem to matter. TC shutdown and restart does not work. Instead, I'm required to hard boot my machine. I'm hung just trying to access the static welcome page of any app, although I do know that init() of the webapp I'm working on is being called. Eric On Fri, 5 Nov 2004 15:43:28 -0800, Eric Wulff [EMAIL PROTECTED] wrote: Linux FC2 TC 5.0.28 I'm not storing a db object within a session although I am storing objs within the session(of course - session.setAttribute). However, I have references to them from the controller so that shouldn't be the problem... eh? An interesting thing, I sometimes have to reboot my machine, not just restart TC. Although other apps run fine, I have to reboot my machine in order to get TC up again. I optimized my db connection, I did have it in servlet init(). Although I knew I had to do this and I'm much better off for it, and I appreciate you're noting it, but this didn't eliminate the crashing problem. I also am now taking advantage of a connection pool. However, as you figured, that does not solve the crash problem. Finally, I removed the session-configsession-timeout element from myapp web.xml to test if this is the initiator of the problem. Let you know what I find. Still, even if this is what initiates the sequence leading to a crash, it shouldn't so something need be fixed/optimized. Any other ideas? Eric On Fri, 5 Nov 2004 13:03:27 -, Steve Kirk [EMAIL PROTECTED] wrote: -Original Message- From: Eric Wulff [mailto:[EMAIL PROTECTED] Sent: Friday 05 November 2004 07:01 To: Tomcat Users List Subject: session-timeout means tomcat restart Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasource connection pool take care of this? I would say that rather than the problem being JDBC hardcoded in the servlet, the problem is more likely to be _how_ that code is written. if it really is the session timeout that is causing this, it sounds to me like you are storing the database objects within a session object (which seems a bit unusual). or at least the last reference to them is stored there, so that when the session is destroyed, the database connection is lost. it might be better to store the objects in local variables within doPost if your servlet is simple, or if it's more complex, then perhaps better places to put them would be the servlet context, or a field of the servlet class/instance. it all depends on your particular situation. whichever you choose though, you must make sure that connections are closed (or returned to the pool) when you have finished with them. this generally involves careful use of try/catch/finally. if restarting the webapp fixes the problem, it could be that your database objects are initialised in the servlet init() method, which is then called again when the webapp restarts. but if this were the case then I'm not sure how session timeout could cause the problem that you describe. datasource connection pooling is not necessarily the answer. you can still use up all your database resources and/or leave them hanging whether you pool them or not! 2. Often tomcat hangs without responding at all, to static or dynamic requests, after it's been left for an hr or more with no interaction. Might this be related to the memory leaks I hear about? you don't say which platform/ versions you are using so memory leaks are hard to comment on. IMHO the issues above are more likely to be the problem so check those first before suspecting an error in TC :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
INFO: connection Timeout reached
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 there anyway I can stop Tomcat from logging these messages as it makes it impossible to see any other messages since they scroll off the console too quickly? Regards Roger __ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
session-timeout means tomcat restart
Hi, I'm experiencing 2 interesting problems that may be related to my session timeout. 1. It seems that when my session times out I need to restart tomcat, often just the application via reload in the manager, in order to gain access to my db again. Could this be because I've been accessing the db via jdbc hard coded in the servlet? Might using a datasource connection pool take care of this? 2. Often tomcat hangs without responding at all, to static or dynamic requests, after it's been left for an hr or more with no interaction. Might this be related to the memory leaks I hear about? thx Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache2 + mod_jk2 on FreeBSD - default socket timeout (bug?)
Hi there, I've got a problem with mod_jk2 and Apache2 under FreeBSD and I think it is a bug. I configured mod_jk2 for two Tomcat servers. If one of these machines is down (unplugging the network cable), mod_jk2 should send all requests to the server that kept running. That is working 90 percent of the time, but sometimes forwarding the request takes about 75 seconds. I found out that this is the default socket timeout of FreeBSD. The problem is that I configured mod-jk2 the way, that it has its own timeout for connecting (see attached workers2.properties). But this value is not recognized. If I decrease the default connect timeout for FreeBSD (by /etc/sysctl.conf), mod_jk2 will use this value and everything is fine. But I don't want to decrease that value, it could cause other problems. So I think it is a bug, that mod_jk2 is not using the timeout values from its workers2.properties in FreeBSD. Btw exactly the same setup for Apache2 and mod_jk2 works fine on Linux. Regards, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache2 + mod_jk2 on FreeBSD - default socket timeout (bug?)
Ok, and here is the attachment. I also forgot to mention that FreeBSD has the version 5.x and Tomcat the version 5. Michael -- [logger] level=DEBUG [shm] file=/tmp/shmFile # Defines a load balancer named lb. [lb:lb] [workerEnv:] info=Global server options timing=1 # Example socket channel, override port and host. [channel.socket:192.168.1.124:8009] tomcatId=camenzind timeout=1 # Example socket channel, override port and host. [channel.socket:192.168.1.123:8009] tomcatId=haller timeout=1 # define the worker 1 [ajp13:192.168.1.124:8009] channel=channel.socket:192.168.1.124:8009 # define the worker 2 [ajp13:192.168.1.123:8009] channel=channel.socket:192.168.1.123:8009 # Mapping my URI to Tomcats [uri:/myURI*] group=lb [status:] info=Status worker, displays runtime information [uri:/jkstatus/*] info=The Tomcat /jkstatus handler group=status: -Original Message- From: Michael Diener [mailto:[EMAIL PROTECTED] Sent: Dienstag, 26. Oktober 2004 09:41 To: [EMAIL PROTECTED] Subject: Apache2 + mod_jk2 on FreeBSD - default socket timeout (bug?) Hi there, I've got a problem with mod_jk2 and Apache2 under FreeBSD and I think it is a bug. I configured mod_jk2 for two Tomcat servers. If one of these machines is down (unplugging the network cable), mod_jk2 should send all requests to the server that kept running. That is working 90 percent of the time, but sometimes forwarding the request takes about 75 seconds. I found out that this is the default socket timeout of FreeBSD. The problem is that I configured mod-jk2 the way, that it has its own timeout for connecting (see attached workers2.properties). But this value is not recognized. If I decrease the default connect timeout for FreeBSD (by /etc/sysctl.conf), mod_jk2 will use this value and everything is fine. But I don't want to decrease that value, it could cause other problems. So I think it is a bug, that mod_jk2 is not using the timeout values from its workers2.properties in FreeBSD. Btw exactly the same setup for Apache2 and mod_jk2 works fine on Linux. Regards, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session-timeout is out by factor of 100?
Hi, How are you checking the time remaining for a session? Yoav Shapira Millennium Research Informatics -Original Message- From: Peter Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, September 20, 2004 12:24 AM To: Tomcat Users List Subject: session-timeout is out by factor of 100? Hi, Is anyone successfully using the web.xml session timeout configuration with Tomcat 5.0.25? Testing seems to indicate that this setting is out by a factor of 100 however using session.setMaxInactiveInterval seems to yield the desired result. E.g. Printing the time remaining (in ms) in a session when using: session.setMaxInactiveInterval(180) // 3 min in seconds --- presents 179226 == ~3 min however, setting session-config session-timeout5/session-timeout /session-config --- presents 29992101 == ~500min Thanks, PJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session-timeout is out by factor of 100?
Yoav, Thanks for replying, long timeLeft = session.getLastAccessedTime() + session.getMaxInactiveInterval() * 1000 - System.currentTimeMillis(); PJ On Mon, 2004-09-20 at 22:54, Shapira, Yoav wrote: Hi, How are you checking the time remaining for a session? Yoav Shapira Millennium Research Informatics -Original Message- From: Peter Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, September 20, 2004 12:24 AM To: Tomcat Users List Subject: session-timeout is out by factor of 100? Hi, Is anyone successfully using the web.xml session timeout configuration with Tomcat 5.0.25? Testing seems to indicate that this setting is out by a factor of 100 however using session.setMaxInactiveInterval seems to yield the desired result. E.g. Printing the time remaining (in ms) in a session when using: session.setMaxInactiveInterval(180) // 3 min in seconds --- presents 179226 == ~3 min however, setting session-config session-timeout5/session-timeout /session-config --- presents 29992101 == ~500min Thanks, PJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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: session-timeout is out by factor of 100?
Found the issue ... my apologies for wasting ppls time. A colleague had added a setMaxInactiveInterval statement in another section of the code which was overriding the web.xml value. Worse was that he'd set it for 3 thinking it was supposed to be in ms. My apologies all and thanks Yoav for looking into it. PJ On Tue, 2004-09-21 at 08:00, Peter Johnson wrote: Yoav, Thanks for replying, long timeLeft = session.getLastAccessedTime() + session.getMaxInactiveInterval() * 1000 - System.currentTimeMillis(); PJ On Mon, 2004-09-20 at 22:54, Shapira, Yoav wrote: Hi, How are you checking the time remaining for a session? Yoav Shapira Millennium Research Informatics -Original Message- From: Peter Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, September 20, 2004 12:24 AM To: Tomcat Users List Subject: session-timeout is out by factor of 100? Hi, Is anyone successfully using the web.xml session timeout configuration with Tomcat 5.0.25? Testing seems to indicate that this setting is out by a factor of 100 however using session.setMaxInactiveInterval seems to yield the desired result. E.g. Printing the time remaining (in ms) in a session when using: session.setMaxInactiveInterval(180) // 3 min in seconds --- presents 179226 == ~3 min however, setting session-config session-timeout5/session-timeout /session-config --- presents 29992101 == ~500min Thanks, PJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
session-timeout is out by factor of 100?
Hi, Is anyone successfully using the web.xml session timeout configuration with Tomcat 5.0.25? Testing seems to indicate that this setting is out by a factor of 100 however using session.setMaxInactiveInterval seems to yield the desired result. E.g. Printing the time remaining (in ms) in a session when using: session.setMaxInactiveInterval(180) // 3 min in seconds --- presents 179226 == ~3 min however, setting session-config session-timeout5/session-timeout /session-config --- presents 29992101 == ~500min Thanks, PJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk timeout/retrys when one load balaced server is down
Title: Nachricht Hello, we are using mod_jk as a load balancer in front of 2 tomcats which are not running on the same server as the apache/mod_jk (the tomcats are actualy in another net zone after a firewall but that should not be important). When one of the tomcats fails the failover to the other server works fine after 3-5 Seconds. But if the whole host goes down (Network cable plugged out, Host switched off) the failover takes ~60 Seconds, because themod_jk tries to connect about 6-10 times with the tomcat and runs into a timeout every time. After that the failover works. But after a few minutes the whole process starts again and some of the users have to wait 60 Seconds before the website appears. So how do i set the timeout to a lower value? Or can i at leased set the retry to 1 or so? Gruß Markus KretzerSystem AdministrationBuhl Data Service GmbHAm Siebertsweiher 3/5, 57290 NeunkirchenTel.: +49 (2735) 776-469Fax.: +49 (2735) 776-310mailto:[EMAIL PROTECTED]http://www.buhl.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
unexpected timeout during benchmark
Hi, I want to measure the performance of a Servlet that I wrote. To have a number to compare with i wrote a servlet which does only a single println in its doget method. When i measure the throughput of this servlet with ab using this arguments: ab -n 2 -c 10 http://localhost:8080/Messung1/TestServlet I receive: .. Completed 14000 requests apr_poll: The timeout specified has expired (70007) Total of 15861 requests completed The jvm is defenitly not out of memory, (top says 50m of -Xmx170m are used) no garbage collection is performed during the test. After some minites of waitung the servlet answers again (no tomcat restart neccessary) What causes this timeout? (when running with half the amout of requests, the throughput is 500/sec) Regards, Henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: unexpected timeout during benchmark
Hi, Maybe all the request processing threads are busy and the accept queue is full? Check your Connector configuration and increase these parameters if needed to allow your test to complete. Yoav Shapira Millennium Research Informatics -Original Message- From: Henrik Rathje [mailto:[EMAIL PROTECTED] Sent: Thursday, September 09, 2004 12:05 PM To: [EMAIL PROTECTED] Subject: unexpected timeout during benchmark Hi, I want to measure the performance of a Servlet that I wrote. To have a number to compare with i wrote a servlet which does only a single println in its doget method. When i measure the throughput of this servlet with ab using this arguments: ab -n 2 -c 10 http://localhost:8080/Messung1/TestServlet I receive: .. Completed 14000 requests apr_poll: The timeout specified has expired (70007) Total of 15861 requests completed The jvm is defenitly not out of memory, (top says 50m of -Xmx170m are used) no garbage collection is performed during the test. After some minites of waitung the servlet answers again (no tomcat restart neccessary) What causes this timeout? (when running with half the amout of requests, the throughput is 500/sec) Regards, Henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
