1. Does using XA instead of local transactions have any significant performance penalty?
Almost always this is the case. Reasons for this are varied, but at the very least, the 2PC protocol always adds overhead. This is one of those times where you have to ask yourself...'Do I really, really, really need XA?' Typical XA scenarios are JMS, or as you laid out mutliple DB access in a single transaction. 2) is there anything wrong with deploying database "A" twice to JBoss, once as a <local-tx-datasource> (for the 95% of cases) and once as an <xa-datasource> (for the 5% of cases)? Not at all. While this is not a typical use case (it's usually either/or), there is nothing wrong with this and given your requirements, seems to make the most sense. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954274#3954274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954274 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
