2 Replies Latest reply on Mar 30, 2012 12:19 PM by jbertram

Transaction error!!!. Internal Exception: javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state

maferji Mar 30, 2012 12:08 PM

Hi everyone!

I’m having a trouble, with an enterprise application in Jboss 7.1.1 Final. The application deploys fine. But in execution time I have the next error:

Caused by: Exception [EclipseLink-23005] (Eclipse Persistence Services - 2.2.0.v20100716-r7835): org.eclipse.persistence.exceptions.TransactionException
Exception Description: Error binding to externally managed transaction
Internal Exception: javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state
        at org.eclipse.persistence.exceptions.TransactionException.errorBindingToExternalTransaction(TransactionException.java:71) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.transaction.AbstractTransactionController.bindToCurrentTransaction(AbstractTransactionController.java:118) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.transaction.AbstractTransactionController.registerSynchronizationListener(AbstractTransactionController.java:411) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerWithTransactionIfRequired(UnitOfWorkImpl.java:4402) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.internal.jpa.transaction.JTATransactionWrapper.registerUnitOfWorkWithTxn(JTATransactionWrapper.java:90) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.internal.jpa.EntityManagerImpl.getActivePersistenceContext(EntityManagerImpl.java:1583) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.internal.jpa.EntityManagerImpl.getActiveSession(EntityManagerImpl.java:1087) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.internal.jpa.EntityManagerImpl.find(EntityManagerImpl.java:614) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.internal.jpa.EntityManagerImpl.find(EntityManagerImpl.java:495) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:193) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
        at MyBean.find(MyBean.java:51) [MyJar.jar:]
        at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source) [:1.6.0_31]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_31]
        at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_31]
        at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:202) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        ... 206 more
Caused by: javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:370)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:351)
        at org.eclipse.persistence.transaction.JTATransactionController.registerSynchronization_impl(JTATransactionController.java:92) [eclipselink.jar:2.2.0.v20100716-r7835]
        at org.eclipse.persistence.transaction.AbstractTransactionController.bindToCurrentTransaction(AbstractTransactionController.java:114) [eclipselink.jar:2.2.0.v20100716-r7835]
        ... 233 more

I had a similar problem with this application migrating to Jboss 5.1 and the solution was set in the jbossts-properties.xml the next instruction:

<property name="com.arjuna.ats.jta.allowMultipleLastResources" value="true"/>

, but Jboss 7.1.1 don’t have this configuration file.

I tried to set a system property in the standalone.xml file with this parameter, but didn’t work .

<system-properties>

<property name="com.arjuna.ats.arjuna.allowMultipleLastResources" value="true"/>

</system-properties>

This application can´t use XA datasourses.

Any ideas to solve this problem? I appreciate a lot any help to fix this problem. Tanks in advance!

Manuel.

1. Re: Transaction error!!!. Internal Exception: javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state

smarlow Mar 30, 2012 12:15 PM (in response to maferji)

Can you attach more from your as7/standalone/log/server.log (include a few pages worth from before the error and after). What does your persistence.xml contain?

I'm also curious how you worked around https://bugs.eclipse.org/bugs/show_bug.cgi?id=365704. Did you write special integration code so that Eclipse could lookup/access the JBoss transaction manager?
Actions
2. Re: Transaction error!!!. Internal Exception: javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state

jbertram Mar 30, 2012 12:19 PM (in response to maferji)

From what I can tell, AS 7.x doesn't support enlisting multiple 1pc (i.e. "last") resources into an XA (i.e. JTA) transaction. There is no option on the configuration schema related to this.

The best way around this issue is to actually use XA resources, but you indicate that is not possible.

The next way around this issue is to remove the transaction altogether. Setting "com.arjuna.ats.jta.allowMultipleLastResources" to "true" and then enlisting multiple 1pc resources into the transaction essentially cripples the transaction semantics anyway so removing the transaction altogether is not a big step beyond this. It looks like your using an EJB3. Assuming that's true and assuming you're using container-managed transactions then you can just use the NOT_SUPPORTED transaction attribute.
Actions

Go to original post