-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
If we force Mod_cluster to use an explicit jvmRoute by editing standalone-ha.xml in this way:
<server xmlns="urn:jboss:domain:1.0"> ... <extensions> ... </extensions> <system-properties> <property name="jboss.mod_cluster.jvmRoute" value="perf22node"/> </system-properties> <management> ...
JSESSIONID returned as a cookie to a client contains this (note the doubled jvmRoute):
Session was created! JSESSIONID - R4PL5AAmojvW0zWd9Ddp86Qs.perf22node.perf22node
On the other side, perf22node log says:
[org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: perf22node
I tried to modify the SystemPropertyJvmRouteFactory.java so as to know what jvmRoute it gets:
public String createJvmRoute(Engine engine) { final String defaultJvmRoute = this.factory.createJvmRoute(engine); final String property = this.property; PrivilegedAction<String> action = new PrivilegedAction<String>() { public String run() { String jvmRoute = System.getProperty(property, defaultJvmRoute); log.info("Info HELL: "+jvmRoute); return jvmRoute; } }; return AccessController.doPrivileged(action); }
And the result in perf22node log says:
[org.jboss.modcluster.SystemPropertyJvmRouteFactory] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Info HELL: perf22node
So it appears it is OK as far as SystemPropertyJvmRouteFactory goes...