Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345268 - JDBCSessionManager does not work with maxInactiveInterval = -1
Summary: JDBCSessionManager does not work with maxInactiveInterval = -1
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.4.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jan Bartel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-10 09:27 EDT by Rüdiger Herrmann CLA
Modified: 2011-11-08 17:23 EST (History)
4 users (show)

See Also:


Attachments
Test project to demonstrate the bug (8.79 KB, application/octet-stream)
2011-05-10 09:30 EDT, Rüdiger Herrmann CLA
no flags Details
Same as attachment #1 but using Derby instead of H2 (8.78 KB, application/octet-stream)
2011-05-12 04:08 EDT, Rüdiger Herrmann CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-05-10 09:27:33 EDT
The JDBCSessionManager does not reload sessions when it was configured with setMaxInactiveInterval( -1 ), which is the default vaue.
Instead of deserializing the existing session, a new session is created.
Please consult the attached test project for a demonstration. To run the project, Jetty, H2, JUnit (3.x) adn javax.servlet is required.
Comment 1 Rüdiger Herrmann CLA 2011-05-10 09:30:03 EDT
Created attachment 195212 [details]
Test project to demonstrate the bug

The make the test succeed, uncomment the line setMaxInactiveInterval... in createJettyServer()
Comment 2 Greg Wilkins CLA 2011-05-11 22:45:33 EDT
Any chance you can convert that test to use derby?
Comment 3 Rüdiger Herrmann CLA 2011-05-12 04:08:02 EDT
Created attachment 195465 [details]
Same as attachment #1 [details] but using Derby instead of H2
Comment 4 Jan Bartel CLA 2011-07-04 04:09:15 EDT
Fixed in jetty-7 svn rev 3461.