search

bossadvisors / memcached-session-manager

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

Notify HttpSessionListeners and HttpSessionActivationListeners when loading a session from memcached #38

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The servlet spec #SRV.7.7.2 "Distributed Environments" says:

"Containers must notify any session attributes implementing the 
HttpSessionActivationListener during migration of a session. They must 
notify listeners of passivation prior to serialization of a session, and of 
activation after deserialization of a session."

This semantics should be supported by the msm-javolution-serializer.

Original issue reported on code.google.com by martin.grotzke on 19 Feb 2010 at 2:07

GoogleCodeExporter commented 9 years ago 
Changed title as this is independent of the actual serialization strategy.

Original comment by martin.grotzke on 19 Feb 2010 at 8:51

GoogleCodeExporter commented 9 years ago 
Passivation does not occur as (right now) sessions are still kept in the local 
session 
map, only activation has to be supported (in the case that a session is loaded 
from a 
tomcat taking over the session from a failed tomcat).

Original comment by martin.grotzke on 19 Feb 2010 at 8:54

GoogleCodeExporter commented 9 years ago 
Just as a personal note (stumbled over this right now):
https://issues.apache.org/bugzilla/show_bug.cgi?id=48717

Original comment by martin.grotzke on 1 Apr 2010 at 7:23

GoogleCodeExporter commented 9 years ago 
Fixed. Also javax.servlet.http.HttpSessionListeners are notified (via 
sessionCreated(HttpSessionEvent)) about the new 
active session in this web application.

Original comment by martin.grotzke on 2 Apr 2010 at 8:47