search

baiheqiang / memcached-session-manager

Automatically exported from code.google.com/p/memcached-session-manager
0 stars 0 forks source link

Check how session relocation might cause issues with applications bound to the session id #39

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Wicket has an AbstractHttpSessionStore.SessionBindingListener class 
(implementing HttpSessionBindingListener and Serializable) that stores the 
session id. When valueUnbound is invoked by the servlet container, the 
SessionBindingListener invokes 
application.getSessionStore().unbind(sessionId) which in turn cleans up the 
PageStore (used by the SecondLevelCacheSessionStore) and the 
bufferedResponses held by the WebApplication.

The question is what does happen when a session is relocated and therefore 
the session id is changed.

Original issue reported on code.google.com by martin.grotzke on 22 Feb 2010 at 8:25

GoogleCodeExporter commented 8 years ago 
This should also make into some kind of documentation or faq.

Original comment by martin.grotzke on 22 Feb 2010 at 8:29