RE: Help with session-timeout
Thanks Rob. I'll keep this investigation open. It's really annoying me. David A. Morrow Technical Systems Lead Autodata Solutions Company [EMAIL PROTECTED] http://www.autodata.net * PLEASE NOTE THAT EFFECTIVE DEC 1,2005 MY TELEPHONE NUMBER WILL CHANGE * NEW !!! Tel: (519) 963-3020 Fax: (519) 451-6615 Poor planning on your part does not necessarily constitute an emergency on my part! This message has originated from Autodata Solutions. The attached material is the Confidential and Proprietary Information of Autodata Solutions. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete this message and notify the Autodata system administrator at [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Rob Dickey [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 29, 2005 2:23 PM To: Dave Morrow Cc: 'Tomcat Users List' Subject: RE: Help with session-timeout Are there any other services involved (JDBC, etc.) that are referenced by or in the session, or where the sessions are dependent? Just wondering why TC threads are invalidating the session... Another option to test is add a line of code in your login process (whatever establishes the HttpSession object) and manually set the timeout with the HttpSession.setMaxInactiveInterval() method. I believe this method overrides any descriptor settings. Of course, having said all of that, your descriptors should work as you have specified. Perhaps the multiple applications or other service timeout descriptors are influencing the session timeouts...I've seen stranger things happen...you might find this link useful as a test of your TC session timeout setup... http://www.jguru.com/faq/view.jsp?EID=127074 HTH, Rob -Original Message- From: Dave Morrow [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 29, 2005 10:48 AM To: Tomcat Users List Subject: Help with session-timeout Hi all. I have a server with multiple applications running under Tomcat 5.5 In TOMCAT_HOME/conf/web.xml session-timeout is set to 30 In TOMCAT_HOME/webapps/myapp/WEB-INF/web.xml session-timeout is set to -1 (infinite) Users are being timed out of their sessions after 30 minutes as opposed to never being timed out. Can anyone assist with this? Any help would be greatly appreciated. David A. Morrow Technical Systems Lead Autodata Solutions Company [EMAIL PROTECTED] http://www.autodata.net * PLEASE NOTE THAT EFFECTIVE DEC 1,2005 MY TELEPHONE NUMBER WILL CHANGE * NEW !!! Tel: (519) 963-3020 Fax: (519) 451-6615 Poor planning on your part does not necessarily constitute an emergency on my part! This message has originated from Autodata Solutions. The attached material is the Confidential and Proprietary Information of Autodata Solutions. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete this message and notify the Autodata system administrator at [EMAIL PROTECTED] mailto:[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]
Help with session-timeout
Hi all. I have a server with multiple applications running under Tomcat 5.5 In TOMCAT_HOME/conf/web.xml session-timeout is set to 30 In TOMCAT_HOME/webapps/myapp/WEB-INF/web.xml session-timeout is set to -1 (infinite) Users are being timed out of their sessions after 30 minutes as opposed to never being timed out. Can anyone assist with this? Any help would be greatly appreciated. David A. Morrow Technical Systems Lead Autodata Solutions Company [EMAIL PROTECTED] http://www.autodata.net * PLEASE NOTE THAT EFFECTIVE DEC 1,2005 MY TELEPHONE NUMBER WILL CHANGE * NEW !!! Tel: (519) 963-3020 Fax: (519) 451-6615 Poor planning on your part does not necessarily constitute an emergency on my part! This message has originated from Autodata Solutions. The attached material is the Confidential and Proprietary Information of Autodata Solutions. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete this message and notify the Autodata system administrator at [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
RE: Help with session-timeout
Are there any other services involved (JDBC, etc.) that are referenced by or in the session, or where the sessions are dependent? Just wondering why TC threads are invalidating the session... Another option to test is add a line of code in your login process (whatever establishes the HttpSession object) and manually set the timeout with the HttpSession.setMaxInactiveInterval() method. I believe this method overrides any descriptor settings. Of course, having said all of that, your descriptors should work as you have specified. Perhaps the multiple applications or other service timeout descriptors are influencing the session timeouts...I've seen stranger things happen...you might find this link useful as a test of your TC session timeout setup... http://www.jguru.com/faq/view.jsp?EID=127074 HTH, Rob -Original Message- From: Dave Morrow [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 29, 2005 10:48 AM To: Tomcat Users List Subject: Help with session-timeout Hi all. I have a server with multiple applications running under Tomcat 5.5 In TOMCAT_HOME/conf/web.xml session-timeout is set to 30 In TOMCAT_HOME/webapps/myapp/WEB-INF/web.xml session-timeout is set to -1 (infinite) Users are being timed out of their sessions after 30 minutes as opposed to never being timed out. Can anyone assist with this? Any help would be greatly appreciated. David A. Morrow Technical Systems Lead Autodata Solutions Company [EMAIL PROTECTED] http://www.autodata.net * PLEASE NOTE THAT EFFECTIVE DEC 1,2005 MY TELEPHONE NUMBER WILL CHANGE * NEW !!! Tel: (519) 963-3020 Fax: (519) 451-6615 Poor planning on your part does not necessarily constitute an emergency on my part! This message has originated from Autodata Solutions. The attached material is the Confidential and Proprietary Information of Autodata Solutions. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete this message and notify the Autodata system administrator at [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
