ActiveMQ Burst Unmatched Confirmation
WARN | Async error occurred: javax.jms.JMSException: Unmatched acknowledge: MessageAck {commandId = 30, responseRequired = false, ackType = 2, consumerId = ID:PC02-DT-009-52405-1421153309991-1:3:10:1, firstMessageId = ID:PC02-DT-009-52360-1421152976467-1:4:11:1:1, lastMessageId = ID:PC02-DT-009-52360-1421152976467-1:4:11:1:1, destination = queue://DATA.DESTINATION, transactionId = null, messageCount = 1, poisonCause = null}; Could not find Message-ID ID:PC02-DT-009-52360-1421152976467-1:4:11:1:1 in dispatched-list (start of ack)
javax.jms.JMSException: Unmatched acknowledge: MessageAck {commandId = 30, responseRequired = false, ackType = 2, consumerId = ID:PC02-DT-009-52405-1421153309991-1:3:10:1, firstMessageId = ID:PC02-DT-009-52360-1421152976467-1:4:11:1:1, lastMessageId = ID:PC02-DT-009-52360-1421152976467-1:4:11:1:1, destination = queue://DATA.DESTINATION, transactionId = null, messageCount = 1, poisonCause = null}; Could not find Message-ID ID:PC02-DT-009-52360-1421152976467-1:4:11:1:1 in dispatched-list (start of ack)
at org.apache.activemq.broker.region.PrefetchSubscription.assertAckMatchesDispatched(PrefetchSubscription.java:482)
at org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:214)
at org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:426)
at org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:408)
at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:77)
at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:77)
at org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:287)
at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:87)
at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:508)
at org.apache.activemq.command.MessageAck.visit(MessageAck.java:236)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
atorg.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
This is the exception I am getting in the activeMQ log. Scenario: I have 10 consumers and I have 100 messages in a destination queue that consumers are listening to. Consumers retrieve messages in 10-20 messages, but eventually stop receiving messages from the queue with the above exception. I understand that a new message will only be provided to the consumer when the confirmation is returned (if I am correct, that is). JMS container:
<jms:listener-container container-type="default" connection-factory="jmsConsumerConnectionFactory"
acknowledge="auto">
<jms:listener destination="DATA.DESTINATION" ref="jmsMessageListener" concurrency="10-15" method="onMessage"/>
</jms:listener-container>
Any help is greatly appreciated, thanks!
source to share
Ok, let me thank me for the answer. Apparently consumers were facing some exceptions when connecting to the DB via httpclient which killed all consumer threads. Anyway, anyone who has this problem without any exceptions can try to solve, 1. Increase the memory limit in the activeMQ configuration "conf / activemq.xml" 2. Try changing the confirmation method to "transaction" or confirm in the message itself message.acknowledge ();
source to share