[
https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl...
]
Radoslav Husar edited comment on MODCLUSTER-469 at 8/24/17 10:29 AM:
---------------------------------------------------------------------
I can confirm the issue can be reproduced on Tomcat 8.0.46, the tomcat 8.5 and 9 are not
affected.
was (Author: rhusar):
I can confirm the issue can be reproduced on Tomcat 8.0.46, the tomcat 8.5 seems correct.
Tomcat8 standalone : jvmRoute not added to jessionid cookie when
generated as UUID by JvmRouteFactory
-----------------------------------------------------------------------------------------------------
Key: MODCLUSTER-469
URL:
https://issues.jboss.org/browse/MODCLUSTER-469
Project: mod_cluster
Issue Type: Bug
Components: Core & Container Integration (Java)
Affects Versions: 1.3.1.Final
Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone
Reporter: Eric Vernier
Assignee: Radoslav Husar
If jvmRoute attribute is not set in server.xml on engine element, ModClusterService
generates a jvmRoute (UUID). This UUID is not added in the value of the cookie
"jsessionid", so the sticky session doesn't work. When the jvmRoute is
defined in the server.xml all works fine.
I known no much about lifecyle in Catalina, but my feeling is that ModClusterService
generates the jvmRoute (with JvmRouteFactory)
after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When
ModClusterService injects the generated jvmRoute it's too, the SessionIdGenerator is
already created.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)