Good and bad news If I increase networkTTL on the multicast network connector on every broker (=3 in my example) everybody receives messages from everybody. This is good. Bad: lots of duplicate messages!
roxanac wrote: > > Another experiment that I've tried: > > 3 brokers in network1 (discovering each other through multicast) > 3 brokers in network2 (discovering each other through multicast) > > I choose one broker from each network to be central point having a static > network connector > to the central point from the other network (pointing to the same port I > use for multicast) > <networkConnectors> > <networkConnector uri="multicast://default?group=local2"/> > <networkConnector uri="static://(tcp://Broker3':61616)" > name = "toOutside" > duplex = "false" > networkTTL = "2"/> > </networkConnectors> > > ntw1 > > ntw2 > > Broker1 > > Broker1' > ^ > > ^ > | > > | > | (multicast) (static, one-way) > > | > | --------------> Broker3 ==============> Broker3' <--------| > | <============== > > | > | > > | > v > > v > Broker2 > > Broker2' > > > Now Broker3' receives all the messages from network1 and Broker3 receives > all the messages from network2, but the rest of the brokers still receive > only messages from their network > (if I increase networkTTL on the static connection I will only get > duplicate messages at Broker3&3', but the other brokers cannot receive > anything from the other network) > > So what can I do for Broker3 to actually FORWARD the messages from > network2 in its own network? > > -- View this message in context: http://old.nabble.com/Pls-help%21-Making-two-networks-working-together-tp28015144p28026641.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
