You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by penguinone <pe...@gmail.com> on 2009/09/25 02:50:10 UTC
ActiveMQ Failover exception
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.
Re: ActiveMQ Failover exception
Posted by penguinone <pe...@gmail.com>.
Also, I believe that we are using auto acknowledge. We're using
mule-config.xml, and I haven't specified an acknowledgment scheme.
--
View this message in context: http://www.nabble.com/ActiveMQ-Failover-exception-tp25604966p25618296.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ Failover exception
Posted by Bruce Snyder <br...@gmail.com>.
On Thu, Sep 24, 2009 at 6:50 PM, penguinone <pe...@gmail.com> wrote:
>
>
> 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)
Hmm, I'm not sure what this would be yet. What acknowledgement mode
are you using? Are you seeing any redelivery of messages?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: ActiveMQ Failover exception
Posted by penguinone <pe...@gmail.com>.
No, not seeing multiple messages. However, what I noticed just now i that it
seems to be after some period of inactivity. And maybe that's just because
part of the call stack contains a class called "InactivityMonitor."
at
org.apache.activemq.broker.region.PrefetchSubscription.assertAckMatchesDispatched(PrefetchSubscription.java:442)
at
org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:188)
at
org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:373)
at
org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:462)
at
org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:194)
at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
at
org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:85)
at
org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:456)
at org.apache.activemq.command.MessageAck.visit(MessageAck.java:205)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:305)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:179)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:143)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:206)
penguinone wrote:
>
>
> We're seeing on both 5.2 and 5.3.
>
> I have to check to see if we're getting duplicate messages. I don't think
> so but I have to check the logs when I get in.
>
>
> rajdavies wrote:
>>
>> Which version of ActiveMQ ?
>> On 25 Sep 2009, at 01:50, penguinone wrote:
>>
>>>
>>>
>>> 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.
>>>
>>
>> Rob Davies
>> http://twitter.com/rajdavies
>> I work here: http://fusesource.com
>> My Blog: http://rajdavies.blogspot.com/
>> I'm writing this: http://www.manning.com/snyder/
>>
>>
>>
>>
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/ActiveMQ-Failover-exception-tp25604966p25617837.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ Failover exception
Posted by penguinone <pe...@gmail.com>.
We're seeing on both 5.2 and 5.3.
I have to check to see if we're getting duplicate messages. I don't think so
but I have to check the logs when I get in.
rajdavies wrote:
>
> Which version of ActiveMQ ?
> On 25 Sep 2009, at 01:50, penguinone wrote:
>
>>
>>
>> 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.
>>
>
> Rob Davies
> http://twitter.com/rajdavies
> I work here: http://fusesource.com
> My Blog: http://rajdavies.blogspot.com/
> I'm writing this: http://www.manning.com/snyder/
>
>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/ActiveMQ-Failover-exception-tp25604966p25614790.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ Failover exception
Posted by Rob Davies <ra...@gmail.com>.
Which version of ActiveMQ ?
On 25 Sep 2009, at 01:50, penguinone wrote:
>
>
> 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.
>
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/