Tom Jenkinson [
http://community.jboss.org/people/tomjenkinson] created the discussion
"Re: Remote txinflow: XID changes"
To view the discussion, visit:
http://community.jboss.org/message/630524#630524
--------------------------------------------------------------
Certainly we are adding this for remoting in the first instance so we want it to play
nicely with that!
One issue is the diamond question, e.g.
-> TM2
TM1 -> TM4
-> TM3
If we don't know the parent then both TM2 and TM3 will potentially try to recover TM4
for all indoubt transactions related to transactions initiated at TM1 which will have
undesirable recovery results.
The other point is the bqual must have the EIS (JNDI) name in it as we have had introduced
this functionality for customers before to assist them in debugging transaction related
issues so we would definitely need to maintain this. That said, you were able to get 600
resources into 3 bytes (out of the 64 available) so I dont anticipate leaving space for
the name being an issue (so long as we have a delimiter).
Finally, I maybe am not understanding your proposal correctly, a worked example would
help. What I can't quite understand is how the address space of the bqual will work in
a pyramid.
e.g:
-> TM2 -> RM1
TM1 -> TM3 -> RM2
-> RM3
Can you let me know what the resource number of each of the TMs and RMs are in that
picture so I can understand a little more clearly?
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/630524#630524]
Start a new discussion in JBoss Transactions Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]