[ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ] Takayoshi Kimura updated JBAS-4893: ----------------------------------- Component/s: Clustering -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ] Takayoshi Kimura updated JBAS-4893: ----------------------------------- Description: 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. was: 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 * 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ] Brian Stansberry updated JBAS-4893: ----------------------------------- Fix Version/s: JBossAS-5.0.1.CR1 (was: JBossAS-5.0.0.CR1) -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4893?page=comments#action_12414186 ] Takayoshi Kimura commented on JBAS-4893: ---------------------------------------- Another scenario: * 3 nodes cluster * If primary node is crashed, subsequent requests bounds between the other 2 nodes. -- 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

[ https://jira.jboss.org/jira/browse/JBAS-4893?page=com.atlassian.jira.plug... ] 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. -- 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