-
1. Re: XAException
kturner75 Sep 12, 2002 10:07 AM (in response to kturner75)I have pasted a portion of the stack trace below. The error code is "XAER_NOTA" which means "The XID is not valid". Note that all transactions are committed successfully if the transaction for session bean "C" is successful. It's only when the session bean "C" transaction fails that I get the XAException.
XAException: tx=XidImpl [FormatId=257, GlobalId=actek-kturner//3, BranchQual=] errorCode=XAER_NOTA
javax.transaction.xa.XAException
at org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl.start(XAResourceImpl.java:258)
at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1087)
at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:614)
at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:111)
at org.jboss.pool.jdbc.xa.XAConnectionFactory.prepareObject(XAConnectionFactory.java:290)
at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:566)
at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:538)
at org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:178)
at com.actek.j2ee.common.util.ConnectionFactory.getConnection(ConnectionFactory.java:47)
at com.actek.j2ee.common.util.ConnectionFactory.getConnection(ConnectionFactory.java:78)
at com.actek.j2ee.common.util.ConnectionFactory.getConnection(ConnectionFactory.java:67) -
2. Re: XAException
adrian.brock Sep 12, 2002 11:22 AM (in response to kturner75)Which version of JBoss do you have, looks like 2.x?
XAER_NOTA means an invalid XID (transaction id)
it looks like the XID for the second invocation of B
is the same as the XID for the failed transaction in C
I'm guessing this from
actek-turner//3 which suggests it is the third transaction
started.
Try configuring TRACE logging for
org.jboss.ejb.plugins
this should show the transaction starts/commits/rollbacks
unless you have an old version that didn't include
this logging.
Regards,
Adrian -
3. Re: XAException
kturner75 Sep 12, 2002 1:11 PM (in response to kturner75)I am running JBoss 2.4.3 against SQLServer 2000 with Opta2000 4.14 JDBC driver. This may be a bug with the JDBC driver. I searched the revision history of the driver and 4.11 had this description:
"The error 'The Xid is not valid.' with JBoss was fixed."
Apparently it's not fixed for the scenario I described. This was logged to Opta support.
I will try to set the log options to TRACE as you described. Thanks. -
4. Re: XAException
kturner75 Sep 12, 2002 7:57 PM (in response to kturner75)The problem was in my "DataSourceClass" attribute setting for my connection pool in the jboss.jcml file. I was using the old XA wrapper class "org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImpl" instead of "org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl". When I changed this attribute, I no longer get the XAException.