What you're describing sounds like what I warned about in my last paragraph: messages are getting routed to broker1 while the consumer is offline, which means they exist in broker1's message store and not anywhere else in the network of brokers. When broker1 goes offline, those messages don't exist anywhere in the network of brokers, so they can't be delivered when the consumer reconnects. Once broker1 comes back online, they reappear in the network of brokers and are delivered to the consumer (even if the consumer is still on broker2).
If you can't afford to have previously-sent messages not delivered (and potentially delivered out of order, since messages sent after broker1 goes down will be delivered while it's down) while a broker is offline, you need to use the master/slave broker configuration instead of a cluster. On Thu, Nov 6, 2014 at 10:49 AM, jeremy11 <liav.el...@gmail.com> wrote: > thanks for the quick answer. my problem with the virtual topic with 2 > brokers > is this: > consumer has a failover url of the 2 brokers, brokers are connected in > duplex mode, replayWhenNoConsumers="true" > > 1. I have a consumer connected to broker1 > 2. each message that is sent to broker 1 or 2 is received by the consumer > on > broker 1 > 3. consumer goes offline > 4. messages (persist) are sent to broker 1 when consumer is down. > 5. broker 1 goes down > 6. consumer goes on line and connects to broker 2 - does not receive the > messages that were sent to broker 1 when the consumer was offline > 7. broker 1 goes online and only then the consumer which is connected to > broker 2 gets the messages > > thanks again! > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Network-of-brokers-as-a-cluster-tp4687028p4687030.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
