I've been reading the discussions about the oracle XA transaction problems - http://www.geocrawler.com/mail/msg.php3?msg_id=9807858&list=10766 - Thank you so much for addressing the oracle XA problems. We have the exact same problems and I'm following your advice to set the <track-connection-by-tx> to true. For that I need to have jboss-3.2 though. I've build jboss-3.2.0beta2 (from cvs) and it looks your deployment descriptors have been added to this. I guess I now just need to deploy the oracle-xa-ds.xml (no longer the oracle-xa-service.xml)? I did this and got:
13:33:42,921 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
MBeans waiting for classes:
MBeans waiting for other MBeans:
I Depend On: jboss.jca:service=XATxDS,name=XAOracleDS
Depends On Me: , ObjectName: jboss.jca:service=XATxDS,name=XAOracleDS
I Depend On: jboss.jca:service=RARDeployment,name=Minerva JDBC XATransaction ResourceAdapter
Depends On Me: jboss.jca:service=XATxCM,name=XAOracleDS
Is jboss-3.2.0beta2 the version I'm supposed to use? Any idea what I'm doing wrong? Our app depends heavily on XA's spanning JMS queues and oracle so I we really need to get a jboss version up in which this stuff works...
This is the code in my oracle-xa-ds.xml:
<!-- The following optionally turns on the TrackConnectionByTx property
of XATxConnectionManager. This property creates a 1 to 1 mapping of
JDBC connections to transactions and prevents a connection from
participating in more than one transaction at the same time. Setting this
to true seems to fix quite a few Oracle XA bugs. -->
<!-- Not needed?
Any help is greatly appreciated!