Description of problem:
There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g.
When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b".
This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks.
Tom Jenkinson <email@example.com> updated the status of jira JBTM-2575 to Closed
Verified with 6.4.8.CP.CR2 and Narayana in version 4.17.32.Final
The behavior was checked with reproducer at
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.