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 <r...@devco.net> 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 >> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/ThreeBrokerTopicNetworkTest.java?view=log >> >> and: https://issues.apache.org/activemq/browse/AMQ-2704 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: http://www.pastie.org/1060648 > > 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: > http://old.nabble.com/Correct-way-to-build-a-mesh-of-brokers-tp29255162p29267890.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
