There is no XA transaction concept with respect to JBoss :-) XA in general simply uses a 2-Phase-Commit (2PC) protocol for multi-resource all or nothing transactions.
A central transaction manager (in jboss case a simple in-JVM transaction manager) first issues a prepare call on all affected resources (databases, JMS resource) enlisted in that transaction. Whitin the prepare call all resources try to do most of the internal - possibly failing - work for a transaction e.g. data writing to disk, but simply not 'activating' these changes yet. If all resources can successfully prepare the transaction, the transaction manager issues the actual commit command to all resources in a second commit call to all resource. If only one resource cannot prepare the transaction, the transaction manager issuess a rollback command to all already prepared resources. That's it. Regards Ulf View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880573#3880573 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880573 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
