On Tue, May 29, 2012 at 8:02 AM, R.I.Pienaar <r...@devco.net> wrote: > > > ----- Original Message ----- > > From: "Mohit Anchlia" <mohitanch...@gmail.com> > > To: users@activemq.apache.org > > Sent: Tuesday, May 29, 2012 3:58:47 PM > > Subject: Re: Sync between 2 queues accross DC > > > > On Tue, May 29, 2012 at 1:02 AM, Dejan Bosanac <de...@nighttale.net> > > wrote: > > > > > Network connector acts as a regular consumer, the message is > > > dispatched to it and it'll ack that it have which will cause the > > > local > > > broker to remove it. > > > > > > > Thanks! Is it intelligent enough to forward the message to only that > > broker that has consumer instead of sending the message to a broker that > > might not have a consumer? > > There is a fantastic blog post @ > http://www.jakubkorab.net/2011/11/understanding-activemq-broker-networks.html > that should cover almost everything you might want to know. >
This indeed is a very good blogpost. Thanks for the link! It looks like if I set networkconnector as duplex from broker1 -> broker2 then I don't really need another networkconnector from broker2 -> broker1. > > Brokers - in general - only get sent data if there are consumers on those > brokers interested in the data. There are some configs settings that > affect > this behaviour though. > > Read that blog post, should clear things up. >
