activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: activemqmessageconsumer duplicate dispatch on connection
Date Thu, 22 Sep 2016 13:18:03 GMT
You're hitting one of a two possible problems.

Most likely, you need to enable the replayWhenNoConsumers option described
in the Stuck Messages section of

You could also be hitting the max allowable number of times the message can
be forwarded between networked brokers (which is confusingly called TTL
even though it has nothing to do with time).  The networkTTL option
described in the NetworkConnector Properties section of that same page
controls that behavior.


On Sep 22, 2016 7:04 AM, "MariscaJane" <> wrote:

> hello guys
> this is my first post
> i want to ask about activemq
> i have 2 broker instances
> i sent queue to broker A,now there is 1000 in broker A.
> when i activate (turn on) the consumer(the consumer had a method failover)
> the queue started to be consumed by the consumer, after that i turn off
> (disconected) broker A, now the consumer move to brokers B.
> then i turn on the broker A, and the broker A started to delivery pending
> message to broker B.
> after all message pending has been transferred to broker B, i turn off the
> broker B, now the consumer move to brokers A, and then i turn on broker B
> BUT, the pending message in broker B didnt move to broker A
> when i see the log, there is a message like this "activemqmessageconsumer
> duplicate dispatch on connection"
> anyone know how to solve this problem ?
> thank you so much
> --
> View this message in context:
> activemqmessageconsumer-duplicate-dispatch-on-connection-tp4716779.html
> Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message