[
https://issues.jboss.org/browse/JBTM-1157?page=com.atlassian.jira.plugin....
]
Tom Jenkinson resolved JBTM-1157.
---------------------------------
Fix Version/s: (was: 5.0.0.Final)
Resolution: Deferred
Hi Clebert, at our offsite we decided that this was not a piece of functionality that
would be best residing in the transaction manager. Our API already allows pieces of logic
to allocate and persistently store (or any other way of allocating a node id) the node id
and as the space available for this id in an XidImple is only 24 bytes we did not feel
that we could generate a guarenteed globally unique id in 24 bytes so felt it better for
the deployer to create ids unique within their application domain.
Tom
Assign an unique NodeID automatically
-------------------------------------
Key: JBTM-1157
URL:
https://issues.jboss.org/browse/JBTM-1157
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Clebert Suconic
Assignee: Tom Jenkinson
It shouldn't be needed to assign the node-id manually IMO.
You could store the node-id on a file and recover it for subsequent starts.
On hornetQ for instance, we look for the nodeID on a file, if the file doesn't exist
we assign a UUID and write to the file.
In our previous experience UUID would be a best fit to assign the nodes since that was
the only way we could guarantee unique IDs between the nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira