Hi,
in case of multiple interconnected brokers you need to use
"suppressDuplicateTopicSubscriptions"
attribute (see for more info
http://activemq.apache.org/networks-of-brokers.html). Also "priority network
dispatch policy" should be used as explained here
https://issues.apache.org/jira/browse/AMQ
Thanks for replying.
Yes i have try true and false on the topic setting and still i get duplicates.
If some has a 7 broker "hub/spoke" model configuration setting it
would be awsome.
So here is more information.
does this make sense? All 6 spoke machines have network connections
to each other.
Try turning conduit subscriptions on
http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-WhentouseandnotuseConduitsubscriptions
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
A
All,
I have been testing the spoke hub model and i have yet to be able to
get a setup that does not duplicate messages if network TTL is greater
than 1. Does anyone have any insight into Topics and network of
brokers???
Thanks
On Thu, Aug 4, 2011 at 11:53 AM, David Fischer(Gtalk)
wrote:
> All
All,
I currently for a network of brokers setup and running with queues
fine. The problem that i am running into is the following:
brokerA <=> brokerB <=> brokerC
if i create a topic pub on brokerA i cannot see the messages on
brokerC with out adding networkTLL > 1. If i do this then as i add
