JBoss Messaging has introduced a requirement that all nodes in a cluster be given a unique id (see http://jira.jboss.com/jira/browse/JBMESSAGING-1121). Since we now have the requirement I'd like to brainstorm a bit about how that id could be used across all cases in the AS where we want to uniquely identify nodes. The obvious one that comes to mind is the Tomcat jvmRoute. For now, let's assume that the JBM unique id is represented by system property "server.peer.id". (Also assume we'll come up a more generic name for the property.) A simple thing to do would be to hard code the following into the std server.xml: <Engine name="jboss.web" defaultHost="localhost" jvmRoute="${server.peer.id:0}> Downside to that is we now dot append the id (or default 0) to every session id, even if we aren't using JK. That's probably no big deal; anyone see a reason why it would be? If it is a problem, perhaps we could leave the jvmRoute attribute out of server.xml and programatically call Engine.setJvmRoute() if the TomcatDeployer's useJK property is set to true. That seems pretty clunky though. Note that JBM requires that the id be a non-negative integer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098951#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...