Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345395 - Session restart may result in stale session singletons
Summary: Session restart may result in stale session singletons
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 345232 345702
  Show dependency tree
 
Reported: 2011-05-11 06:58 EDT by Rüdiger Herrmann CLA
Modified: 2011-05-18 08:33 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-05-11 06:58:10 EDT 
If a session is restarted (usually by sending a request that contains a startup=xxx parameter), the current implementation of LifeCycleServiceHandler#clearSessionStore() does only remove all session attributes.
Attributes from the ServiceStore remain untouched. With the current implementation of SessionSingletonBase that buffers instances in the SessionStore, this may lead to instances from the old session still being returned in the new session.
Comment 1 Rüdiger Herrmann CLA 2011-05-18 08:33:03 EDT 
This issue is solved with committing the changes for bug 345702. The new session singleton implementation does not buffer instances in the ServiceStore any more.