We set up our active MQ to fail over (failover://(host1:61616,host2:61616)).
I'm getting these fairly frequently, and I've only seen them related to
memory in other people's posts. Unlikely to be this case as I'm operating in
a low volume test environment. Any leads as to what else might be the
problem?
WARN Service - Async error occurred:
javax.jms.JMSException: Unmatched acknowledege: MessageAck {commandId = 71,
responseRequired = false, ackType = 2, consumerId =
ID:domU-12-31-38-01-89-01-48240-1253838130518-0:55:1:1, firstMessageId =
null, lastMessageId =
ID:domU-12-31-38-01-89-01-48240-1253838130518-0:68:1:1:1, destination =
queue://queue.MOBLAH, transactionId =
TX:ID:domU-12-31-38-01-89-01-48240-1253838130518-0:55:22, messageCount = 3};
Could not find Message-ID
ID:domU-12-31-38-01-89-01-48240-1253838130518-0:68:1:1:1 in dispatched-list
(end of ack)
javax.jms.JMSException: Unmatched acknowledege: MessageAck {commandId = 71,
responseRequired = false, ackType = 2, consumerId =
ID:domU-12-31-38-01-89-01-48240-1253838130518-0:55:1:1, firstMessageId =
null, lastMessageId =
ID:domU-12-31-38-01-89-01-48240-1253838130518-0:68:1:1:1, destination =
queue://queue.MOBLAH, transactionId =
TX:ID:domU-12-31-38-01-89-01-48240-1253838130518-0:55:22, messageCount = 3};
Could not find Message-ID
ID:domU-12-31-38-01-89-01-48240-1253838130518-0:68:1:1:1 in dispatched-list
(end of ack)
at
org.apache.activemq.broker.region.PrefetchSubscription.assertAckMatchesDispatched(PrefetchSubscription.java:444)
at
org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:208)
at
org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:377)
--
View this message in context:
http://www.nabble.com/ActiveMQ-Failover-exception-tp25604966p25604966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
