activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From artnaseef <>
Subject Re: Request / Reply in Network of Brokers
Date Thu, 08 May 2014 03:17:46 GMT
Is this with the default Network TTL setting of 1?  Sounds like that's the
case and that  decreaseNetworkConsumerPriority is false (also the default).

So, even though the consumer is only on A, and a person can easily see it
makes no sense to move the messages to broker B, in an ActiveMQ
demand-forwarded network-of-brokers, brokers B and C are both going to
create consumers as the means to allow consumers across the network to
consume the messages, and to allow that consumer on Broker A to receive
messages produced on the other brokers, causing messages to move from Broker
A to Broker B.  With the default round-robin delivery of messages, exactly
half will go to broker A's immediate consumer, and the other half will go to
broker B.

Broker B will not return those messages to Broker A, nor forward them on to
Broker C, due to exhaustion of the Network TTL of 1.

Your best bet is to use the decreaseNetworkConsumerPriority=true which never
sends messages to another broker when there is another local consumer.

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message