WildFly Transaction Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
{{External|https://access.redhat.com/solutions/771963}} | {{External|https://access.redhat.com/solutions/771963}} | ||
The transaction manager service is configured with a node identifier. If there are more than one nodes in a cluster, that value has to be changed to something unique per node. The procedure is described here: | The transaction manager service is configured with a node identifier. If there are more than one nodes in a cluster, that value has to be changed to something unique per node. The procedure is described here: {{Internal|WildFly_Transaction_Subsystem_Configuration#Set_Unique_Node_Identifier|Set Unique Node Identifier}} | ||
Latest revision as of 16:28, 7 June 2017
Internal
Node Identifier
The transaction manager service is configured with a node identifier. If there are more than one nodes in a cluster, that value has to be changed to something unique per node. The procedure is described here: