3 Replies Latest reply on Jan 11, 2009 6:51 AM by jade_king

problem with oracle xa

jade_king Jan 5, 2009 1:41 AM

[com.arjuna.ats.internal.jta.transaction.arjunacore.xastart] [com.arjuna.ats.internal.jta.transaction.arjunacore.xastart] TransactionImple.enlistResource - xa_start - caught: XAException.XA_RETRY for

Previous Exception will be occured with a-xa-ds.xml file(Two JNDI with same jdbc url was configured in the a-xa-ds.xml file
)
If I use different url wiht different JNDI ,no exception occured

Code Flow:
1.tx begin
2.select from 1st datasource
3.select from 2st ds
4.insert with 1st ds
5.tx commit

any advice will be appreciated!

PS: pad=true is not exist in jboss as 5

1. Re: problem with oracle xa

jade_king Jan 7, 2009 9:25 PM (in response to jade_king)

jbosstm is still in version 4.2.3.doesn't support 5.0.0GA?

thanks
Actions
2. Re: problem with oracle xa

jhalliday Jan 8, 2009 6:17 AM (in response to jade_king)

> jbosstm is still in version 4.2.3.doesn't support 5.0.0GA?

http://www.jboss.org/community/docs/DOC-10804
Actions
3. Re: problem with oracle xa

jade_king Jan 11, 2009 6:51 AM (in response to jade_king)

Caused by: org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -53e76f96:12b3:4969d963:6a status: ActionStatus.ABORT_ONLY >)
at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:409)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:625)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:499)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
... 53 more
Caused by: javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -53e76f96:12b3:4969d963:6a status: ActionStatus.ABORT_ONLY >
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TransactionSynchronization.checkEnlisted(TxConnectionManager.java:879)
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConnectionManager.java:675)
at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:403)
... 57 more
2009-01-11 19:39:40,758 WARN [org.hibernate.util.JDBCExceptionReporter] (WorkerThread#0[]) SQL Error: 0, SQLState: null
2009-01-11 19:39:40,759 ERROR [org.hibernate.util.JDBCExceptionReporter] (WorkerThread#0[ ]) Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -53e76f96:12b3:4969d963:6a status: ActionStatus.ABORT_ONLY >); - nested throwable: (org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -53e76f96:12b3:4969d963:6a status: ActionStatus.ABORT_ONLY >))

thanks jhalliday ,I try it as your advice, but it doesn't work
Actions

Go to original post