gzilla/show_bug.cgi?id=24774
session timeout working only once
--- Additional Comments From [EMAIL PROTECTED] 2004-06-23 21:38 ---
PersistentManagerBase has already been patched (see Bug 23468).
As for the reasoning, I am afraid I can't shed any light on th
gzilla/show_bug.cgi?id=24774
session timeout working only once
--- Additional Comments From [EMAIL PROTECTED] 2004-06-22 22:50 ---
my suggestion would be to handle such situation in
PersistentManagerBase.processExpires; so that even if custom implementat
gzilla/show_bug.cgi?id=24774
session timeout working only once
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=20083
Session timeout implementation requires 2 accesses per timeout.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=26261
Another session timeout problem (similar to 25234)
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=26261
Another session timeout problem (similar to 25234)
Summary: Another session timeout problem (similar to 25234)
Product: Tomcat 5
Version: 5.0.16
Platform: Other
OS/Version: Other
Status: NEW
Severity:
gzilla/show_bug.cgi?id=10656
Session Timeout incorrect for 0 in web.xml
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PRO
gzilla/show_bug.cgi?id=11745
web.xml session-timeout value of 0 does not work as specified.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=25792
Session timeout implemented incorrectly
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=25792
Session timeout implemented incorrectly
--- Additional Comments From [EMAIL PROTECTED] 2003-12-30 14:29 ---
The session timeout in Tomcat seems to be implemented in a way that doesn't take
the background clean-up thread into account.
StandardSession has tw
gzilla/show_bug.cgi?id=25792
Session timeout implemented incorrectly
--- Additional Comments From [EMAIL PROTECTED] 2003-12-29 10:32 ---
Created an attachment (id=9725)
webapp to reproduce the bug
-
To unsubscribe, e-mail:
gzilla/show_bug.cgi?id=25792
Session timeout implemented incorrectly
Summary: Session timeout implemented incorrectly
Product: Tomcat 5
Version: 5.0.16
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Major
Pr
gzilla/show_bug.cgi?id=10656
Session Timeout incorrect for 0 in web.xml
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=24774
session timeout working only once
--- Additional Comments From [EMAIL PROTECTED] 2003-11-21 17:06 ---
some additional information:
sorry, i have forgot to mention what this SessionMonitor is:
this is our custom object which implements HttpSessionBindingLi
gzilla/show_bug.cgi?id=24774
session timeout working only once
--- Additional Comments From [EMAIL PROTECTED] 2003-11-18 10:22 ---
Created an attachment (id=9152)
propsed patch
-
To unsubscribe, e-mail: [EMAIL PROTECTE
gzilla/show_bug.cgi?id=24774
session timeout working only once
Summary: session timeout working only once
Product: Tomcat 4
Version: Nightly Build
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority:
hi,
i'm having this problem:
1. after x mins of inactivity, user session is invalidated
(PersistentManagerBase.processExpires)
2. StandardSession.expire does setValid(false) and expiring=true at the
beginning
3. then it calls StandardSession.removeAttribute ->
SessionMonitor.valueUnbound -> Sta
gzilla/show_bug.cgi?id=7613
session timeout setting ignored/confusing to configure
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=7613
session timeout setting ignored/confusing to configure
--- Additional Comments From [EMAIL PROTECTED] 2002-08-28 16:52 ---
I updated the session manager's TC5 documentation to remove mentioning the
maxInactiveInterval attribute (since setting it is pointle
is
inherited
- automatically if you specify a
<session-timeout>
-element in the web application deployment descriptor
-(/WEB-INF/web.xml).
-
-
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
gzilla/show_bug.cgi?id=11745
web.xml session-timeout value of 0 does not work as specified.
Summary: web.xml session-timeout value of 0 does not work as
specified.
Product: Tomcat 4
Version: 4.0.4 Final
Platform: PC
OS/Version: Wind
Hi,
This came up on the xdoclet-devel mailing list. The xdoclet
implementation takes follows the dtd saying that a session expires if
the session-timeout is =< 0, while the spec says it will never expire if
session-timeout is -1, Tomcat says it will not expire if session-timeout
is <
gzilla/show_bug.cgi?id=10656
Session Timeout incorrect for 0 in web.xml
--- Additional Comments From [EMAIL PROTECTED] 2002-07-10 19:33 ---
True, and page 222 of Servlet 2.3 says that Session.getMaxInactiveInterval()
must return a negative to indicate that the session never times out
gzilla/show_bug.cgi?id=10656
Session Timeout incorrect for 0 in web.xml
Summary: Session Timeout incorrect for 0 in web.xml
Product: Tomcat 4
Version: 4.0.3 Final
Platform: Other
OS/Version: Other
Status: NEW
Severity:
gzilla/show_bug.cgi?id=7613
session timeout setting ignored/confusing to configure
--- Additional Comments From [EMAIL PROTECTED] 2002-06-27 04:19 ---
Robert, what you say reflects the behavior that I've been seeing.
If the ability to set the session timeout using a Context or Man
gzilla/show_bug.cgi?id=7613
session timeout setting ignored/confusing to configure
--- Additional Comments From [EMAIL PROTECTED] 2002-06-26 21:29 ---
Verified in 4.1.5The only current way to set the session timeout is in the
web.xml of the app, or modify the "system" web.x
I'm experiencing exactly this problem as (the original message) below, can
somebody please help.
From: [EMAIL PROTECTED] (Christian Bourque)
Subject: session timeout bug ?
Date: Fri, 7 Sep 2001 13:48:37 -0400
Hi !
I've been searching everywhere for this problem and I just can&
gzilla/show_bug.cgi?id=7613
session timeout setting ignored/confusing to configure
Summary: session timeout setting ignored/confusing to configure
Product: Tomcat 4
Version: Nightly Build
Platform: Other
OS/Version: Other
Statu
Hi there,
I'm using the t4 I built checked out and built on Friday, and I noticed the
following:
java.lang.NoClassDefFoundError:
at .valueUnbound(ServletSession.java:333)
at
org.apache.catalina.session.StandardSession.removeAttribute(StandardSession.
java:953)
at
org.apa
I tried the first approach, it works great with 3.x.
Thank you,
Jayesh
-Original Message-
From: Kief Morris [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 8:26 AM
To: [EMAIL PROTECTED]
Subject: Re: session timeout
Jayesh typed the following on 08:00 AM 1/17/2001 -0800
&g
Jayesh typed the following on 08:00 AM 1/17/2001 -0800
>I need to do some work when tomcat session gets timed out. Could anyone of
>you suggest how I can do it.
With servlet 2.2 (Tomcat 3.x) you should make sure one of the attributes you're
adding to the session implements HttpSessionBindingListe
Hi,
I need to do some work when tomcat session gets timed out. Could anyone of
you suggest how I can do it.
Changing invalidate/expire method would be the last thing I like to do. Is
there any other way (call back method??).
Thanks,
Jayesh
32 matches
Mail list logo
