]
Jean-Frederic Clere commented on JBAS-4893:
-------------------------------------------
Won't be moving the issue to the front-end makes sense. The front-end knows where it
connects to and therefore knows the "new" JVMRoute.
Probably that should be switch able via a parameter in httpd.
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: