Hi Ivan, > From my experience, I would see the TM of server A start a transaction with > some XID then call Server "B". Server "B" would then start a different XID > and do its work. Is this the correct assumption?
You're right. This is what Jboss's transaction manager does. It does not propagate transactional context. As server "B" receives a request without transactional context, it starts a new transaction, completely independent of server "A"'s one. > If so, is there any way to pass the XID to Server "B" so that its committable > resources share the same transaction? Yes, but not using the default TM as it is. You would have to modify it or use a third party implementation (Arjuna, for example, as mentioned in the other reply). > How are commits handled if Server "A" is the source of the commit call? Can > the commit be expected to propagate to Server "B"? What happens if Server "B" > uses resources that Server "A" does not? Well, as there will be two distinct transactions, each one will do 2PC with its own resources. And no commits will be propagated. I hope I've helped. Feel free to contact me if you have any questions... Danilo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865738#3865738 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865738 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
