[jboss-jira] [JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.
[
https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-3042:
-----------------------------------
The point of making it pluggable is that the administrator is in a position to know
whether, for example, the IP address is globally unique within their organization, or
other such schemes. Likewise with a database or other central registry, the administrator
takes on any associated risk as a balance to the effort saved or the risk inherent in
manual maintenance of a large environment.
In a domain, in particular, it is actually impossible to set up a unique ID per server in
a server group (it uses the profile settings) unless you define a system or environment
property on every host which is expanded in that hosts' server (which is potentially
an even greater burden, especially if you have a very large number of servers).
There should be a warning logged if the default value of node
identifier has not been changed.
------------------------------------------------------------------------------------------------
Key: WFLY-3042
URL: https://issues.jboss.org/browse/WFLY-3042
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transactions
Affects Versions: 8.0.0.Final
Environment: JBoss EAP 6.x
Reporter: Tom Ross
Assignee: Gytis Trikleris
JBoss EAP instance is using the value of node identifier to identify XA transactions
that belong to it. By default this value is set to 1. Now days in most environments there
will be multiple JBoss instances sharing XA resources there for it is necessary to set the
value of node identifier to a unique value for each instance. This is something that most
end users fail to perform. Therefor it would be helpful if a warning message was logged
at startup telling the user to do it.
--
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