this behavior is by design, but it could be improved. A network bridge will not forward a message back to where it came from because in the scenario you describe, with a slow consumer, messages would constantly be forward over and back between broker1 and broker2.
I guess an improvement would be to make this behavior configurable and to allow a delay and backoff to be specified so that bouncing messages do not consume all available cpu and network resources. 2009/6/11 yinghe0101 <[email protected]> > > I already put this in a comment on > https://issues.apache.org/activemq/browse/AMQ-2009 which might explain why > people experience this issue. > > I have a simple cause which can cause dispatch problem: > > 1. setup a network of broker1, broker2, bridged by multicast discovery > 2. make a producer send 5 msg to queueA to broker2 > 3. make a consumer to consume from broker1 queueA ( make it slow, so it > only > consumer 1 msg) but make sure all 5 msg from broker2 are forwared to > broker1 > 4. stop the consumer to broke1, restart it to consume from broker2 queueA > 5. the 4 msgs originally published to broker2 and forwarded to broker1 and > has not yet been consumed will stuck on broker1 and will not forwarded to > broker2 for the consumer to consume. > > You can only clear out the 4 left over stuck msg by making consumer consume > from broker1 in this case. > > This is a very critical issue because you might restart your application > many times and run into this. > > I will look into how the demandfowardbridge handles this case. if you know > anything about this, please help. this is very urgent. thanks > > best, > ying > -- > View this message in context: > http://www.nabble.com/Serious-dispatch-issue-tp23990060p23990060.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
