From: <ad...@jb...> - 2004-05-21 21:41:52
|
Your problem looks to be the branch qualifier: 2004-05-21 09:22:31,556 TRACE [org.jboss.tm.TransactionImpl] startResource(XidImpl [FormatId=257, GlobalId=devwkstn15//33, BranchQual=1]) leaving: org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@1c16b30 flags=0 2004-05-21 09:22:32,181 TRACE [org.jboss.tm.TransactionImpl] startResource(XidImpl [FormatId=257, GlobalId=devwkstn15//33, BranchQual=1]) leaving: org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@16e3a7e flags=2097152 MSSQL's two different XAResources (for the two connections) are returning isSameRM=true so JBoss is issuing a TMJOIN rather than TMNOFLAGS. i.e. it is including the work of both connections on the same transaction branch. BUT, MSSQL does not like this (it should if it returns isSameRM true). Oracle has a similar problem, try the fix used there: | <isSameRM-override-value>false</isSameRM-override-value> | Which will force two different transaction branches for the two physical connections (XAResources). The files you mention are irrelevent if you don't use CMP. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835850#3835850 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835850 |