Bhanu created AMQ-3826:
--------------------------
Summary: Lot of unmatched ackowledge warnings
Key: AMQ-3826
URL: https://issues.apache.org/jira/browse/AMQ-3826
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.5.1
Reporter: Bhanu
Hello,
We are getting a lot of these kind of exceptions in broker logs.
activemq.log.2012-02-29:2012-02-29 19:10:32,872 | WARN | Async error occurred:
javax.jms.JMSException: Unmatched acknowledge: MessageAck {commandId = 80173,
responseRequired = false, ackType = 2, consumerId =
ID:desa1186.nyc.deshaw.com-61574-1329905029635-2:3:60:1, firstMessageId = null,
lastMessageId = ID:desb0444.nyc.deshaw.com-49820-1330523262004-0:618:2:1:1,
destination = queue://tca.heartbeat, transactionId = null, messageCount = 1,
poisonCause = null}; Expected message count (1) differs from count in
dispatched-list (2) | org.apache.activemq.broker.TransportConnection.Service |
ActiveMQ Transport: tcp:///10.253.127.196:46192
I did some googling and found that these can occur while using failover(either
by failover API or failover broker). But we are not using any failover in the
setup where these exceptions are occuring. I am not able to reproduce them
either. They occur during the day randomly.
Any ideas on why they are being logged?
Thanks,
Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
