1 Reply Latest reply on Oct 12, 2016 2:24 PM by urbandroid

    javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction.

    afonseca75
    afonseca75 Oct 11, 2016 12:19 PM

      Hi all,

       

      I am using HornetQ under JbossEAP

       

      My configuration XML in JBoss are like bellow

       

      <pooled-connection-factory name="hornetq-ra">

        <transaction mode="xa"/>

        <connectors>

          <connector-ref connector-name="in-vm"/>

        </connectors>

        <entries>

          <entry name="java:/JmsXA"/>

         </entries>

      </pooled-connection-factory>

       

      <jms-queue name="myQueue">

        <entry name="queue/queueName"/>

        <entry name="java:jboss/exported/jms/queue/queueName"/>

      </jms-queue>

       

      In the MDB i am using TransactionType CONTAINER and TransactionAttribute REQUIRED

       

      The MDB is called but a lot of times every message, and looks like the message is not consumed from the queue.

       

      In the JBOSS log I can see

       

      [org.hornetq.ra] (Thread-2 (HornetQ-client-global-threads-1136619173)) HQ152006: Unable to call after delivery: javax.resource.spi.LocalTransactionException: javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction.

       

      [org.hornetq.core.server] (Thread-4 (HornetQ-scheduled-threads-161191419)) HQ222103: transaction with xid XidImpl (161406466 bq:0.0.0.0.0.0.0.0.0.0.-1.-1.-84.16.-12.109.-94.-64.-27.-108.87.-4.-8.-100.0.0.3.6.0.0.0.0.0.0.0.0 formatID:131077 gtxid:0.0.0.0.0.0.0.0.0.0.-1.-1.-84.16.-12.109.-94.-64.-27.-108.87.-4.-8.-100.0.0.3.5.49 base64:AAAAAAAAAAAAAP__rBD0baLA5ZRX_PicAAADBgAAAAAAAAAAAAAAAAAAAAAAAP__rBD0baLA5ZRX_PicAAADBTEHAgIA timed out

       

      I have also tried to use Transaction Type BEAN and Transaction Attribute REQUIRES_NEW without sucess.

       

      Could you please assist in this configuration?

       

      TIA

        • 1. Re: javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction.
          urbandroid
          urbandroid Oct 12, 2016 2:24 PM (in response to afonseca75)

          arjuna only listens resource adapters calls through spi interface methods, i think with high probability there is a problem at your ra conf or usage at mdb. You can try to catch exceptions print stacktrace see the cause of problem. For now all i can say is its "timed out". The cause can be connection configurations or something taking more time than expiration timeout threshold.

           

          Be sure that connection is working if this not the problem show your related mdb code so someone can help.

            • Actions