[
https://issues.jboss.org/browse/WFLY-1119?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on WFLY-1119:
-------------------------------------
OK, that max length thing might be an issue then because a Uid looks to be 28 bytes:
https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes...
The length of the node name is fixed because we use it in the Xid (which imposes a 64 byte
limit). You could have a look at how we construct the Xids to see if there are some
elements of the Uid that are not required because they may already be in the Xid:
https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com...
Assign an unique NodeID automatically
-------------------------------------
Key: WFLY-1119
URL:
https://issues.jboss.org/browse/WFLY-1119
Project: WildFly
Issue Type: Feature Request
Components: Transactions
Reporter: Clebert Suconic
Assignee: Amos Feng
Priority: Optional
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 was sent by Atlassian JIRA
(v6.3.11#6341)