[
http://jira.jboss.com/jira/browse/JBAS-5421?page=all ]
Brian Stansberry moved JBCLUSTER-101 to JBAS-5421:
--------------------------------------------------
Project: JBoss Application Server (was: JBoss Clustering)
Key: JBAS-5421 (was: JBCLUSTER-101)
Component/s: Clustering
Web (Tomcat) service
(was: Web Tier)
Fix Version/s: Backlog
(was: Q3Y8)
Make session clustering's "useJK" handling a pluggable
policy so we can integrate with other load balancers
-----------------------------------------------------------------------------------------------------------
Key: JBAS-5421
URL:
http://jira.jboss.com/jira/browse/JBAS-5421
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: Backlog
Session replication uses the JvmRouteValve to detect session failover and modify the
session id so mod_jk knows to thereafter pin the the session to the new node.
JBossCacheManager also has logic that understands how to strip out the jvmRoute from the
session id.
Need to make this logic a pluggable policy, so we can deal with other load balancers that
may have a different mechanism for tracking to which node a session is pinned.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira