JBoss Community

Re: Remote txinflow: XID changes

created by David Lloyd in JBoss Transactions Development - View the full discussion

Tom Jenkinson wrote:

 

To be clear, the EIS name is the only debugging information in the XID.

 

XID:

formatId

gtrid { sequence, root node name }

bqual { sequence, subordinate node name, parent node name, eis name }

 

sequences are vital naturally

root node name is vital to detect orphans at the root in recovery

subordinate node name is vital to detect orphans at subordinates

parent node name is optional to filter list of recovered XIDs at a remote server by the caller

eis name is debugging

 

Okay so here's where my confusion came in.

 

When I suggested that sequence idea, the thought was that root node + sequence is basically equivalent to (subordinate node name + parent node name) in that any participant should be able to tell whether a branch belonged to it or its descendants, and also should be adequate for filtering recovered XIDs.  But I'm not sure what you mean by "orphans" exactly - aren't all branches normally recovered by the root?  If so, does the subordinate path actually matter?

Reply to this message by going to Community

Start a new discussion in JBoss Transactions Development at Community