[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-3042: ------------------------------------- What I meant, is that we _want_ to support different servers assuming the identity. There is a concept with Narayana that you can run the transaction manager on any machine and point it at an object store (e.g. jdbc one) and give it an identifier to take over from an old server. Narayana itself is pluggable, i.e. it exposes a setXaNodeName method that clients (e.g. subsystem) are free to pass in what they like. The subsystem itself is currently only pluggable in so much as it supports a single implementation that obtains the value to use from the standalone.xml. It would be possible to alter the subsystem to use the IP address etc but as I say, when it boots up on a different machine it will have a different node name so wouldn't take over from the old server. Happy to alter the subsystem but I am not really sure its a good idea to use the IP/port as the ID for the reason I mentioned above. In terms of the alternative (a uuid), I mentioned the reason I was worried to use something random is in case it is lost. Suggestions? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira