RE: Sessions Timeout
I had a quick question about this. For a session to be refreshed by being accessed, does this count only direct calls to the specific URI's, or if I do a forward from another servlet context into it, will this count as access as well. I'd have *expected* any access to the session will put the clock back to start, so to speak. But someone with more in-depth knowledge may know for sure. J. -- You're only jealous cos the little penguins are talking to me. *** For more information on Ordnance Survey products and services, visit our web site at http://www.ordnancesurvey.co.uk *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Sessions Timeout
At 09:40 AM 01/29/2002 +, you wrote: Is there a way to configure Tomcat to check the expire time against last access time and not creation time? Sessions *are* invalidated when the timeout period has passed without access. *Not* when the timeout period has passed from creation. I had a quick question about this. For a session to be refreshed by being accessed, does this count only direct calls to the specific URI's, or if I do a forward from another servlet context into it, will this count as access as well. As far as I can tell, the servlet forwarding does not seem to refresh the session timeout value. I am using Tomcat 3.2.4 with crossContext values enabled. It is sitting on top of Apache 1.3.20 and mod_jk. Thanks in advance, Mario- _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Sessions Timeout
On Wed, 30 Jan 2002, Mario Felarca wrote: Date: Wed, 30 Jan 2002 12:03:56 -0600 From: Mario Felarca [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Sessions Timeout At 09:40 AM 01/29/2002 +, you wrote: Is there a way to configure Tomcat to check the expire time against last access time and not creation time? Sessions *are* invalidated when the timeout period has passed without access. *Not* when the timeout period has passed from creation. I had a quick question about this. For a session to be refreshed by being accessed, does this count only direct calls to the specific URI's, or if I do a forward from another servlet context into it, will this count as access as well. As far as I can tell, the servlet forwarding does not seem to refresh the session timeout value. A session is accessed only when the called servlet calls request.getSession(). When you cross servlet contexts, that *should* still work (I've never actually tried it) -- but you need to remember that there is a separate session in each context. I am using Tomcat 3.2.4 with crossContext values enabled. It is sitting on top of Apache 1.3.20 and mod_jk. Thanks in advance, Mario- Craig -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Sessions Timeout
Hi Jason, the session method getMaxInactiveInterval() gives you the time-value, after that your inactive session is killed. You can change this value in the web.xml file. Anja -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Sessions Timeout
Is there a way to configure Tomcat to check the expire time against last access time and not creation time? Sessions *are* invalidated when the timeout period has passed without access. *Not* when the timeout period has passed from creation. Justin. -- You're only jealous cos the little penguins are talking to me. *** For more information on Ordnance Survey products and services, visit our web site at http://www.ordnancesurvey.co.uk *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Sessions Timeout
the session method getMaxInactiveInterval() gives you the time-value, after that your inactive session is killed. You can change this value in the web.xml file. Or in the jsp - request.getSession.setMaxInactiveInterval(time in seconds). J. -- You're only jealous cos the little penguins are talking to me. *** For more information on Ordnance Survey products and services, visit our web site at http://www.ordnancesurvey.co.uk *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
