Anonymous | Login | Signup for a new account | 10-03-2024 03:54 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0004692 | [Resin] | major | always | 07-31-11 09:31 | 08-04-11 10:26 | ||||
Reporter | mnsh | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 4.0.20 | ||||||
Summary | 0004692: Broken HttpSession.maxInactiveInterval behavior | ||||||||
Description |
Somewhere between 4.0.18 and 4.0.20, session lifetimes stopped working as expected. To reproduce, configure a web-app as follows: <session-config> <use-persistent-store/> <always-save-session>true</always-save-session> <session-timeout>120</session-timeout> </session-config> 1. Unzip the attached jsp:s, and request stest.jsp. Note that maxInactiveInterval changes from 7200 (expected) to 69120 (waay off) when something is jsp:included during the first request. Also note that isNew() is false after the jsp:include. Reloading the page shows that maxInactiveInterval is stuck at 69120. 2. Edit stest.jsp and set doInclude=false. Restart your browser and request stest.jsp again. Note that maxInactiveInterval == 7200 both times (as expected). Now set doSetInterval=true and keep reloading. Note that maxInactiveInterval is 7200 the first time and 1800 the second time. 3. Restart your browser and request/keep reloading stest.jsp. Note that maxInactiveInterval == 1800 this time - it seems that setMaxInactiveInterval() only "sticks" when called during a session's very first request. |
||||||||
Additional Information | |||||||||
Attached Files | stest.zip [^] (780 bytes) 07-31-11 09:31 | ||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
31 total queries executed. 26 unique queries executed. |