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. On 26 July 2010 12:10, ripienaar <r...@devco.net> wrote: > > > > Gary Tully wrote: >> >> set decreaseNetworkConsumerPriority=true because the topic duplicate >> suppression logic depends on priority to remove a duplicate network >> subscription. >> > > > Thanks for your reply, have tried this before, tried again now this is the > setup from one of the 3: > > <networkConnectors> > <networkConnector name="dev3-dev1" > uri="static:(tcp://dev1.xx.net:6166)" networkTTL="3" duplex="false" > decreaseNetworkConsumerPriority="true"/> > <networkConnector name="dev3-dev2" > uri="static:(tcp://dev1.xx.net:6166)" networkTTL="3" duplex="false" > decreaseNetworkConsumerPriority="true"/> > </networkConnectors> > > I've removed all the authentication and authorization from the 3 brokers as > well just in case, a full config from one of them: > http://www.pastie.org/1060266 > > The others just mirror it. > > So with a consumer on dev1, dev2 and dev3 to /topic/foo and producing a > message to the topic on dev3 then dev2 and 1 will both get the message > twice. > -- > View this message in context: > http://old.nabble.com/Correct-way-to-build-a-mesh-of-brokers-tp29255162p29265342.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
