ackType=0 is a delivered ack which is used to increase the prefetch
within a transaction or with individual ack but it is not critical.
The error indicates that the broker does not have knowledge of the
dispatch of that message to the consumer, as a result it has no
message to ack. This can occur after failover if there are pending
acks that get replayed.
On 24 June 2011 10:47, jandeclercq <jan.decle...@alsic.be> wrote:
> Hey,
>
>
> Since I've updated to "Activemq 5.5.0" and my client software to
> "ActiveMQ-CPP 3.4.0" I'm getting this error in my activemq.log now and then:
>
>
> Does anybody knows if this is a bad error? How can I prevent this?
>
>
>
> Thx in advance.
>
>
>
>
> 2011-06-24 09:40:00,784 | WARN |
> org.apache.activemq.broker.TransportConnection.Service | Async error
> occurred: javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 798252, responseRequired =
> false, ackType = 0, consumerId = ID:HMSCDBTEST-53350-1308666544226-0:1:0:0,
> firstMessageId = ID:HMSCDBTEST-35984-1308834459674-3:2:1:981:161,
> lastMessageId = ID:HMSCDBTEST-35984-1308834459674-3:2:1:985:343, destination
> = queue://mvb.outgoing.informix.writeToCDB, transactionId = null,
> messageCount = 500, poisonCause = null} |
> javax.jms.JMSException: Could not correlate acknowledgment with dispatched
> message: MessageAck {commandId = 798252, responseRequired = false, ackType =
> 0, consumerId = ID:HMSCDBTEST-53350-1308666544226-0:1:0:0, firstMessageId =
> ID:HMSCDBTEST-35984-1308834459674-3:2:1:981:161, lastMessageId =
> ID:HMSCDBTEST-35984-1308834459674-3:2:1:985:343, destination =
> queue://mvb.outgoing.informix.writeToCDB, transactionId = null, messageCount
> = 500, poisonCause = null}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:318)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:383)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:549)
> 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:197)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:87)
> at
> org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:464)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:229)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:306)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:179)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:69)
> at
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:203)
> at
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:220)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:202)
> at java.lang.Thread.run(Thread.java:736)
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Could-not-correlate-acknowledgment-since-update-tp3622139p3622139.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http://blog.garytully.com
