Doubled jvmRoute value in JSESSIONID ------------------------------------ Key: MODCLUSTER-249 URL: https://issues.jboss.org/browse/MODCLUSTER-249 Project: mod_cluster Issue Type: Bug Reporter: Michal Babacek Assignee: Paul Ferraro Labels: eap6, mod_cluster If we force Mod_cluster to use an explicit jvmRoute by editing *standalone-ha.xml* in this way: {code:xml} <server xmlns="urn:jboss:domain:1.0"> ... <extensions> ... </extensions> <system-properties> <property name="jboss.mod_cluster.jvmRoute" value="perf22node"/> </system-properties> <management> ... {code} *JSESSIONID* returned as a cookie to a client contains this (note the doubled jvmRoute): {noformat} Session was created! JSESSIONID - R4PL5AAmojvW0zWd9Ddp86Qs.perf22node.perf22node {noformat} On the other side, perf22node log says: {noformat} [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: perf22node {noformat} I tried to modify the [SystemPropertyJvmRouteFactory.java|http://anonsvn.jboss.org/repos/mod_clu...] so as to know what jvmRoute it gets: {code:java} 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); } {code} And the result in perf22node log says: {noformat} [org.jboss.modcluster.SystemPropertyJvmRouteFactory] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Info HELL: perf22node {noformat} So it appears it is OK as far as SystemPropertyJvmRouteFactory goes...