WildFly Transaction Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
{{Internal|WildFly System Properties#jboss.node.name|jboss.node.name}} | {{Internal|WildFly System Properties#jboss.node.name|jboss.node.name}} | ||
Note that "jboss.node.name" has to be explicitly configured at startup. In standalone mode, it can be added in <tt>standalone.conf</tt>: | |||
<pre> | |||
JAVA_OPTS="$JAVA_OPTS -Dstandalone.conf" | |||
</pre> | |||
For domain mode, custom system properties can be declared as described here: | |||
* [[WildFly_System_Properties#Domain_Mode|Declare System Properties in Configuration Files for Domain Mode]] | |||
* [[WildFly_CLI_-_Manipulating_System_Properties#Add.2FRemove_a_per-Server_System_Property|Add/Remove a per-Server System Property with CLI]] | |||
Latest revision as of 17:32, 7 June 2017
Internal
Set Unique Node Identifier
If a unique node identifier is not set in domain mode, you'll get this:
18:55:02,298 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 37) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
To eliminate the warning, configure standalone.xml or domain.xml as follows:
<subsystem xmlns="urn:jboss:domain:transactions:1.5">
<core-environment node-identifier="${jboss.node.name}">
...
</core-environment>
...
</subsystem>
Also see:
Note that "jboss.node.name" has to be explicitly configured at startup. In standalone mode, it can be added in standalone.conf:
JAVA_OPTS="$JAVA_OPTS -Dstandalone.conf"
For domain mode, custom system properties can be declared as described here: