What I described as LRCO is what you've quoted from IBM and Sun. Just some people call them Resources, whereas others call them Participants :-)
The principle is the same: the participant/resource that can't do 2PC has to be the *last* one in the first phase to go off and *only* if all other resources either said read-only, or voted to commit too. But like I said, ordering isn't mandated by JTA, so many implementations don't provide this optimisation or others that are possible via ordering. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822039#3822039 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822039 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
