[
https://jira.jboss.org/jira/browse/JBAS-4893?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-4893:
-----------------------------------
Fix Version/s: JBossAS-6.0.0.Alpha1
(was: JBossAS-5.1.0.Beta1)
Moving issues that won't happen for next AS release after 5.0.0 (whether called 5.0.1
or 5.1.0) to AS 6. It might get pulled back to a 5.x release; just don't want it on
the 5.0.1/5.10 roadmap which to me at this point both might mean "the one after
5.0.0.GA".
JvmRouteValve (UseJK) for non session replication setup
-------------------------------------------------------
Key: JBAS-4893
URL:
https://jira.jboss.org/jira/browse/JBAS-4893
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Takayoshi Kimura
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.Alpha1
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:
* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky
session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another, JSESSIONID won't be
changed
* The node AAA recovered
* The request comes back to the node AAA, lost session again
Enabling JvmRouteValve can prevent last failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira