[
https://issues.jboss.org/browse/JBTM-1989?page=com.atlassian.jira.plugin....
]
Michael Musgrove updated JBTM-1989:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/jbosstm/narayana/pull/504
Uid comparison fails for max uid
--------------------------------
Key: JBTM-1989
URL:
https://issues.jboss.org/browse/JBTM-1989
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Common
Affects Versions: 5.0.0.M6
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.0.0.Final
The largest Uid (Uid.MAX_UID) is defined to have the string form
7fffffff:7fffffff:7fffffff:7fffffff:7fffffff
The first 2 components are hex values corresponding to Integer.MAX_INT but these two
fields end up being converted into 2 longs to populate the field long[] hostAddr hostAddr.
Consequently most Uids will end up being greater than MAX_UID (which causes problems when
trying to order last resources last in the intentions list.
The fix is to use
"7fffffffffffffff:7fffffffffffffff:7fffffff:7fffffff:7fffffff" for MAX_UID
--
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