[
https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-3042:
-----------------------------------
Given how hard it can be to maintain unique numerical identifiers, especially in a large
environment, perhaps it's a good idea to allow a pluggable assignment strategy. Here
are some ideas:
* Central registry such as...
** LDAP database
** DNS entry
** JDBC data store
* Perfect or imperfect hashing strategy such as...
** IP address mapping
** MAC address mapping
** Hardware serial number mapping
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