Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345268

Summary:

JDBCSessionManager does not work with maxInactiveInterval = -1

Product:

[RT] Jetty

Reporter:

Rüdiger Herrmann <ruediger.herrmann>

Component:

server

Assignee:

Jan Bartel <janb>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

janb, jesse.mcconnell, jetty-inbox, ruediger.herrmann

Version:

7.4.0

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
Test project to demonstrate the bug	none
Same as attachment #1 but using Derby instead of H2	none

Description Rüdiger Herrmann

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

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

2011-05-11 22:45:33 EDT

Any chance you can convert that test to use derby?

Comment 3 Rüdiger Herrmann

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

2011-07-04 04:09:15 EDT

Fixed in jetty-7 svn rev 3461.