Closed magro closed 9 years ago
magro
commented
9 years ago From martin.grotzke on February 19, 2010 12:51:27
Changed title as this is independent of the actual serialization strategy.
Summary: Notify HttpSessionActivationListeners when loading a session from memcached
magro
commented
9 years ago From martin.grotzke on February 19, 2010 12:54:48
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).
magro
commented
9 years ago From martin.grotzke on April 01, 2010 00:23:42
Just as a personal note (stumbled over this right now): https://issues.apache.org/bugzilla/show_bug.cgi?id=48717
magro
commented
9 years ago From martin.grotzke on April 02, 2010 13:47:51
Fixed. Also javax.servlet.http.HttpSessionListeners are notified (via sessionCreated(HttpSessionEvent)) about the new active session in this web application.
Summary: Notify HttpSessionListeners and HttpSessionActivationListeners when loading a session from memcached
Status: Fixed
Labels: Milestone-1.3
From martin.grotzke on February 19, 2010 15:07:39
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: http://code.google.com/p/memcached-session-manager/issues/detail?id=38