The servlet specification is a good source of such information.
-Original Message-
From: Paul Wallace [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 5:11 AM
To: [EMAIL PROTECTED]
Subject: session expiry
Hello All,
A simple one? I have my session defined in a servlet thus:
See the servlet specification from java.sun.com.
In particular, session expiration can be set in web.xml.
sessions can also be expired programmatically via its invalidate() method.
Please followup with tomcat-user if you have more questions. This forum is
for changing the internals of tomcat.
Hi,
I debugged thru Tomcat3.2.1 source code this morning and
it too has the same problem:
Session.access() is called only once per request, before the
request is processed (called by findSession in StandardManager)
This would mean that getLastAccessedTime() always gives
the time of (last-1) req
---
> From: Craig R. McClanahan <[EMAIL PROTECTED]>
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Subject: Re: Session-expiry bug? getLastAccessedTime
> Date: Sat, 10 Feb 2001 12:52:24 -0800>
>
Craig R. McClanahan typed the following on 12:52 PM 2/10/2001 -0800
>This was discussed by the expert group for servlet 2.3, and Kief's
>understanding is what we came up with. In addition, that is what Section 7.6
>says in 2.3 PFD (emphasis is added):
>
>The getLastAccessedTime method of the
Kief Morris wrote:
> Murthy Gorty typed the following on 09:59 AM 2/9/2001 -0800
> >I noticed a problem with session timeouts in Tomcat3.2.1
> >The background thread that recycles sessions based on timeouts uses
> >Session.getLastAccessedTime().
> >The session object itself has two variables
> >l
Murthy Gorty typed the following on 09:59 AM 2/9/2001 -0800
>I noticed a problem with session timeouts in Tomcat3.2.1
>The background thread that recycles sessions based on timeouts uses
>Session.getLastAccessedTime().
>The session object itself has two variables
>lastAccessedTime and thisAccesse
