As default, a message can pass through a broker only once.
Since your message has passed through broker A so it won't be replayed
except for your additional requirement.
You can enable replay feature via adding policy for you queue like this:
<policyEntry queue=">" >
<conditionalNetworkBridgeFilterFactory
replayWhenNoConsumers="true"/></policyEntry>
Or you may take a look at the stuck messages section at the page,
http://activemq.apache.org/networks-of-brokers.html
In your use case new messages should be forwarded to the consumer on broker A.
At 2013-03-21 02:43:08,carlzuo <[email protected]> wrote:
>I had two ActiveMQ brokers (A and B) that were configured as store-forward
>network. They work perfectly to forward messages from A to B when there is a
>consumer connected on broker B and producer sends messages to A. The problem
>is that when the consumer is killed and reconnected to A, the queued
>messages on B (they were forwarded from A) won't forward back to A where the
>consumer connected to. Even I send new messages to B, all messages were
>stuck on B until I restart brokers. I have tried to set networkTTL="4" and
>duplex="true" on the broker network connector, but it doesn't work.
>
>
>
>--
>View this message in context:
>http://activemq.2283324.n4.nabble.com/ActiveMQ-network-of-brokers-don-t-forward-messages-back-tp4664973.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
