I have an app that 95% of the time only needs to use one database (call it "A"). The other 5% of the time, it needs to transactionally update both "A" and a second database "B".
Obviously for the latter use case, I need to deploy both "A" and "B" using the <xa-datasource> tag. However I'm concerned that using global transactions will needlessly impact performance for the 95% of cases that only need local transactions. My questions are therefore: 1. Does using XA instead of local transactions have any significant performance penalty? 2. If yes, 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)? I've tried this in a small test app and it seems to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954245#3954245 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954245 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
