activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Correct way to build a mesh of brokers
Date Mon, 26 Jul 2010 15:58:15 GMT
you need to turn duplex off or only create the bridges from one
broker. With your config, where every broker is connected to every
other broker, duplex=true causes every broker to be connected twice to
every other broker!

duplex is handy in a hub-spoke topology where the spoke initiates the
forwarding bridge in duplex mode, negating the need for the hub to be
ware of the spoke.

On 26 July 2010 16:41, ripienaar <> wrote:
> Gary Tully wrote:
>> ok, so you need to set networTTL=2 for your 3 broker mesh (two hops
>> will get to any broker) and enable audit for your topics by explicitly
>> setting a topic destination policy. <policyEntry topic=">" />
>> See the relevant test case: testAllConnectedBrokerNetworkSingleProducerTTL
>> in
>> and: for some more
>> detail
>> If there is still a problem, maybe take ThreeBrokerTopicNetworkTest
>> for a whirl and add your scenario to it.
> Unfortunately I dont know a whole lot of Java so running test cases and
> adding test cases perhaps a bit above what I can do...
> I have tried these options as per pastie:
> Still duplicates, I've tried several permutations:
> - not using duplex, creating the mesh connections all by hand with static
> connections
> - tried to move the order of the policy maps above connectos and network
> connections rather than below.
> All results in dupes.
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


Open Source Integration

View raw message