2 Replies Latest reply: Jan 27, 2011 3:22 AM by Rico Neubauer RSS

JBoss6 - Conflict between EntitySynchronizationInterceptor and Arjuna

Rico Neubauer Novice

Hi all,

 

Currently running some stress tests with JBoss6 (snapshots from 2010-12-15 currently) and perfromance looks very well.

But after  the system is running for some time (12-24 hours), there occur transaction errors. One of them is targeted in HORNETQ-583 but another one seems to be a conflict between the EntitySynchronizationInterceptor and Arjuna, which occurs out of a sudden, without any difference in the executed processes, see stacktrace extract below, will also attach the whole log file.

See Thread#159659 for a description of hardware and test-scenario.

 

Has anyone seen this also or could imagine what causes it?

 

java.lang.IllegalStateException: ARJUNA-16082 Synchronizations are not allowed! Transaction status isActionStatus.ABORTING
   at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:367)
   at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:344)
   at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.register(EntitySynchronizationInterceptor.java:160)
   at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:218)

 

 

Chart.png

  • 1. Re: JBoss6 - Conflict between EntitySynchronizationInterceptor and Arjuna
    jaikiran pai Master
    java.lang.IllegalStateException: ARJUNA-16082 Synchronizations are not allowed! Transaction status isActionStatus.ABORTING
       at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:367)
       at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:344)
       at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.register(EntitySynchronizationInterceptor.java:160)
       at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:218)

    That stacktrace indicates that something before this "register" cause a transaction abort and the EntitySynchronizationInterceptor is trying to register to an aborted transaction. You'll have to track down why the transaction has been aborted.

  • 2. JBoss6 - Conflict between EntitySynchronizationInterceptor and Arjuna
    Rico Neubauer Novice

    Have JBoss6.0_GA running now for about 3 weeks with the same test-case and the problem did not show again, so I assume some change in the final release had a healing influence.