[
http://issues.apache.org/jira/browse/GERONIMO-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461613
]
Gianny Damour commented on GERONIMO-2677:
-----------------------------------------
I attach two patches:
* JETTY-2677.patch: Jetty6 patch in order to simplify the integration code.
** AbstractSessionManager.Session is updated such that its two constructors
share the same logic with respect to the definition of the _id field. Also, the
method initValues is added such that sub-classes can explicitly control the
initialization of the _values field.
** SessionHandler.handle is refactored: the method setRequestedId has been
extracted such that sub-classes can also share this behavior; and
** Request.getSession(boolean) is improved such that a session cookie is set
against a session whose id has changed (following a migration).
* GERONIMO-2677.patch: Geronimo patch to leverage the Jetty6 code base after
having applied the Jetty6 patch.
> HttpSession Relocation - Sticky load-balancing via HTTP Cookie
> --------------------------------------------------------------
>
> Key: GERONIMO-2677
> URL: http://issues.apache.org/jira/browse/GERONIMO-2677
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Clustering
> Reporter: Gianny Damour
> Assigned To: Gianny Damour
> Attachments: GERONIMO-2677.patch, JETTY-2677.patch
>
>
> When an HttpSession is migrated from one node to another:
> * its id must be updated (the worker name suffix is to be set to the name of
> the node owning the HttpSession); and
> * the session cookie must be updated accordingly.
> The worker name suffix, which can be retrieved from the session cookie, can
> be leverage to configure sticky load-balancing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
