[jboss-jira] [JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

[Tom Jenkinson (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated WFLY-10541:
---------------------------------
    Summary: allow user to easily override the transaction node identifier  (was: default transactions node-identifier to jboss.node.name)


> allow user to easily override the transaction node identifier
> -------------------------------------------------------------
>
>                 Key: WFLY-10541
>                 URL: https://issues.jboss.org/browse/WFLY-10541
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Server
>    Affects Versions: 13.0.0.Final
>            Reporter: Brad Maxwell
>            Assignee: Jason Greene
>
> It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine.
> {code}
> WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> {code}
> {code}
>             <subsystem xmlns="urn:jboss:domain:transactions:3.0">
>                 <core-environment node-identifier="${jboss.node.name}">
> {code}
> I was thinking messaging also had property that needed to be set but I am not seeing the warning currently.  Also I have seen if jboss.node.name is not set, then ejb calls may not work as expected, so it would be good to have it warn if it is not set as well.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)