the network will not send messages back to where they came from. This is to stop messages bouncing over and back between brokers if there are consumers on both brokers. The issue is that the network connector (consumer) is quite fast so it will typically beat a regular consumer to a message or get to consume most of them and they will bounce over and back between the brokers.
Am thinking priority may help here but there may be more to it. 2009/1/29 wizeak <[email protected]>: > > I have two brokers connected to each other and when I pass a message to one > of them it stores it and forwards it to the other broker. Great. However, > if I take one of the brokers offline (simulating a server failure/crash) and > queue up a bunch of pending messages on the broker that is still alive, when > I get the second broker back online the pending messages on the first broker > aren't forwarded to the second broker. Is there any type of configuration > that will make the first broker forward all of the pending messages it has > queued to the second broker when it comes back online from being down? I'd > really appreciate any sort of help anyone can offer. Thanks. > -- > View this message in context: > http://www.nabble.com/store-and-forward--not-really%21-help-please%21-tp21736342p21736342.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com
