You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Kevro <ac...@turnsignalfluid.com> on 2006/04/21 16:53:29 UTC

Invalid acknowledgment: MessageAck

Using RC3, just about every message consumed triggers the below exception
from the broker output, and the one after that from the consumer.  I'm using
a non-transacted,  AUTO_ACKNOWLEDGE, session on both ends, with persistent
delivery mode, and only one broker - no master/slave.  Upgrading from RC2 to
RC3 seemed to help it at first, but after restarting the consumer, the
exceptions started flying again.  Since the messages aren't getting
acknowledged, they stay on the queue, and keep getting processed over and
over again whenever the consumer's connection is closed (i.e., after a
restart).  I've also tried using client_acknowledge, with no change.  Any
suggestions?

TIA,
Kevin


INFO  Service                        - Async error occurred:
javax.jms.JMSException: Invalid acknowledgment: MessageAck {commandId = 
 9326, responseRequired = false, ackType = 2, consumerId =
ID:rizzo-37125-1145392777689-1:0:1:1, firstMessageId = null, lastMessageI 
d = ID:rizzo-37125-1145392777689-1:9834:1:1:1, destination =
queue://QUEUE_NAME, transactionId = null, messageCount = 1} 
javax.jms.JMSException: Invalid acknowledgment: MessageAck {commandId =
9326, responseRequired = false, ackType = 2, consumerId = ID 
:rizzo-37125-1145392777689-1:0:1:1, firstMessageId = null, lastMessageId =
ID:rizzo-37125-1145392777689-1:9834:1:1:1, destination = 
queue://QUEUE_NAME, transactionId = null, messageCount = 1} 
        at
org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:186) 
        at
org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:204) 
        at
org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:342) 
        at
org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176) 
        at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:61) 
        at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:61) 
        at
org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:73) 
        at
org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:351) 
        at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178) 
        at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:196) 
        at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62) 
        at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:88) 
        at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:70) 
        at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114) 
        at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) 
        at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87) 
        at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:139) 
        at java.lang.Thread.run(Thread.java:595) 
INFO  PrefetchSubscription           - Could not correlate acknowledgment
with dispatched message: MessageAck {commandId = 9327, res 
ponseRequired = false, ackType = 2, consumerId =
ID:rizzo-37125-1145392777689-1:0:1:1, firstMessageId = null, lastMessageId =
ID:riz 
zo-37125-1145392777689-1:9835:1:1:1, destination = queue://QUEUE_NAME,
transactionId = null, messageCount = 1} 






[2006-04-19 12:05:30.540 tcp:///192.168.1.33:61616 WARN 
activemq.ActiveMQConnection] Async exception with no exception listener:
javax.jms.JMSException: Invalid acknowledgment: MessageAck {commandId =
2064, responseRequired = false, ackType = 2, consumerId =
ID:rizzo-37182-1145458410566-1:0:1:1, firstMessageId = null, lastMessageId =
ID:rizzo-37182-1145458410566-1:7520:1:1:1, destination = queue://QUEUE_NAME,
transactionId = null, messageCount = 1} 
javax.jms.JMSException: Invalid acknowledgment: MessageAck {commandId =
2064, responseRequired = false, ackType = 2, consumerId =
ID:rizzo-37182-1145458410566-1:0:1:1, firstMessageId = null, lastMessageId =
ID:rizzo-37182-1145458410566-1:7520:1:1:1, destination = queue://QUEUE_NAME,
transactionId = null, messageCount = 1} 
        at
org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:186) 
        at
org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:204) 
        at
org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:342) 
        at
org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176) 
        at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:61) 
        at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:61) 
        at
org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:73) 
        at
org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:351) 
        at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178) 
        at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:196) 
        at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62) 
        at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:88) 
        at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:70) 
        at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114) 
        at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) 
        at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87) 
        at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:139) 
        at java.lang.Thread.run(Thread.java:595)
--
View this message in context: http://www.nabble.com/Invalid-acknowledgment%3A-MessageAck-t1486998.html#a4027914
Sent from the ActiveMQ - User forum at Nabble.com.


Re: Invalid acknowledgment: MessageAck

Posted by Johannas Frank <mi...@redbrick.dcu.ie>.
I'm having the same problem with the latest snapshot of activemq using spring
2-M4's async processing. 
--
View this message in context: http://www.nabble.com/Invalid-acknowledgment%3A-MessageAck-t1486998.html#a4415621
Sent from the ActiveMQ - User forum at Nabble.com.