[mod_cluster-issues] [JBoss JIRA] Closed: (MODCLUSTER-148) Automatic generation of jvmRoute leads to non-stickiness

Paul Ferraro (JIRA) jira-events at lists.jboss.org
Mon May 3 12:31:05 EDT 2010


     [ https://jira.jboss.org/jira/browse/MODCLUSTER-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro closed MODCLUSTER-148.
-----------------------------------

    Resolution: Duplicate Issue
      Assignee: Paul Ferraro  (was: Jean-Frederic Clere)


Duplicate of MODCLUSTER-146.

> Automatic generation of jvmRoute leads to non-stickiness
> --------------------------------------------------------
>
>                 Key: MODCLUSTER-148
>                 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-148
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.1.0.CR1
>            Reporter: Bela Ban
>            Assignee: Paul Ferraro
>             Fix For: 1.1.0.CR2
>
>
> When I don't set a jvmRoute in server.xml, the generated jvmRoute BINDADDR:PORT:ENGINE is not correctly appended to a jsessionid, and therefore doesn't preserve stickiness.
> To reproduce:
> - Remove jvmRoute from server.xml
> - Start a few nodes
> - Deploy a webapp which adds stuff to a session
> - Access the webapp a few times
> ==> It is not guaranteed that we hit the same node every time, as there is no stickiness

-- 
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

        


More information about the mod_cluster-issues mailing list