I found out why the msg ack with transactionId=null was sent after the XA
transaction finished processing the same message. When the MessageConsumer
is closed, the method ActiveMQMessageConsumer.deliverAcks() is called.
There is a check if a session's ack mode is auto acknowledge, if the
isAutoAck
I am working on a simple standalone application reading messages from
ActiveMQ and storing them into a database using ActiveMQ 5.7, Spring 3.1.2
(DMLC), and Bitronix Transaction manager 2.1.3. ActiveMQ logs show Unmatched
acknowledge for every message processed in a JTA transaction. Detailed
inspec
