]
Radoslav Husar updated MODCLUSTER-469:
--------------------------------------
Status: Pull Request Sent (was: Pull Request Sent)
Git Pull Request:
Tomcat 8 container integration does not add jvm-route to JSESSIONID
when generated by UUIDJvmRouteFactory
---------------------------------------------------------------------------------------------------------
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, 1.4.0.Alpha1
Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone
Reporter: Eric Vernier
Assignee: Radoslav Husar
Priority: Critical
Fix For: 1.4.0.Alpha2, 2.0.0.Alpha1
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.