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
essageCount = 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
;> dispatched-list
>> (end of ack)
>>at
>> org
>> .apache
>> .activemq
>> .broker
>> .region
>> .PrefetchSubscription
>> .assertAckMatchesDispatched(PrefetchSubscription.java:444)
>>at
>> org
>> .apache
&g
va:
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 Davie
On Thu, Sep 24, 2009 at 6:50 PM, 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 v
ge in context:
http://www.nabble.com/ActiveMQ-Failover-exception-tp25604966p25604966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
