Acknolwedging JMS message in MDB results in errors in JBoss EAP

Issue

• When a MDB (using "Auto-acknowledge" as acknowledgeMode and bound to a topic) calls "message.acknowledge()", several Exceptions (NullPointerException, HornetQException[errorCode=0 message=null]) are thrown. For example, in Red Hat JBoss EAP 5:

ERROR [org.hornetq.core.client.impl.ClientSessionImpl] (Thread-0 (HornetQ-client-global-threads-1228964345)) Caught Exception
HornetQException[errorCode=0 message=null]
        at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:327)
        at org.hornetq.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1387)
        at org.hornetq.core.client.impl.DelegatingSession.end(DelegatingSession.java:333)
        at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:752)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2656)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1784)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:94)
        at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:160)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1433)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.endTransaction(MessageInflowLocalProxy.java:481)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.finish(MessageInflowLocalProxy.java:360)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.after(MessageInflowLocalProxy.java:260)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:141)
        at $Proxy367.afterDelivery(Unknown Source)
        at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:327)
        at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1060)
        at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:53)
        at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1205)
        at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)

ERROR [org.hornetq.core.client.impl.ClientSessionImpl] (Thread-4 (HornetQ-client-global-threads-1228964345)) XA operation failed Cannot start, session is already doing work in a transaction null code:-6

ERROR [STDERR] (Thread-4 (HornetQ-client-global-threads-1228964345)) javax.transaction.xa.XAException
    at org.hornetq.core.client.impl.ClientSessionImpl.start(ClientSessionImpl.java:1676)
    at org.hornetq.core.client.impl.DelegatingSession.start(DelegatingSession.java:513)
    at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:799)
    at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:510)
    at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.startTransaction(MessageInflowLocalProxy.java:416)
    at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.before(MessageInflowLocalProxy.java:236)
    at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:136)
    at $Proxy367.beforeDelivery(Unknown Source)
    at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:307)
    at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1060)
    at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:53)
    at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1205)
    at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)

• An easy fix for us is to remove the "message.acknowledge()" call. However, we would like to have a better exception handling at this place. Only a warning should be displayed in the log. This is a feature request.