Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4692 major always 07-01-11 09:31 08-04-11 10:26
Reporter: mnsh Platform:  
Assigned To: ferg OS:  
Priority: normal OS Version:  
Status: closed Product Version: 4.0.20  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.0.21  
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.
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:  stest.zip [^] (780 bytes) 07-01-11 09:31

Notes
(0005423)
ferg   
08-04-11 10:26   
server/01a2