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.
Hello All,
A simple one? I have my session defined in a servlet thus:
HttpSession session = req.getSession();
session.setAttribute("userSession", h); // (h = HashMap)
how or where do define session parameters such as expiry? I would
ideally like my session to die when I call a spec
On Fri, 14 Sep 2001, David Lecomber wrote:
> Date: Fri, 14 Sep 2001 17:21:06 +0100
> From: David Lecomber <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: StandardManager : Session expiry thread.
>
> [tomcat 4.0
[tomcat 4.0-rc2] It's possible for the session expiring thread to not
catch an exception - thrown within session.expire - which then stops
this thread and means all other sessions are not expired (forever!)
at
org.apache.catalina.session.StandardSession.removeAttribute(StandardSession.ja
Hi,
I posted a question last week about this and I'm including
the conclusions of that posting anticipating more responses.. :-) I'm using
tomcat 3.2.1 final release.
Tomcat's check for Session Expiry happens in a background thread
(StandardManager::processExpire
) request. And the session-expiry thread
looks at the wrong-time. IF getLastAccessedTime() should
return the time of (last-1) request, then perhaps there
should be another method getAccessedTime() that returns
thisAccessedTime in StandardSession and this would be used
by the session-expiry thread
---
> 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
Hi,
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 thisAccessedTime.
-
public
12 matches
Mail list logo
