Hello,
I am trying to create a redundant network of brokers using 3 activemq
instances.
I would ideally have redundant connections like:
- A to B
- A to C
- B to A
- B to C
- C to A
- C to B
This is a typical mesh, can be made simpler if I am able to use duplex
connections:
- A duplex to B
- A duplex to C
- B duplex to C
The problem I have is that if I create a setup like this I always get
duplicate messages on topic,
All the machines have blocks resembling this:
<networkConnectors>
<networkConnector name="dev3-dev2" uri="static:(tcp://dev2:6166)"
userName="amq" password="xx" suppressDuplicateQueueSubscriptions="true"
networkTTL="2"/>
<networkConnector name="dev3-dev1" uri="static:(tcp://dev3:6166)"
userName="amq" password="xx" suppressDuplicateQueueSubscriptions="true"
networkTTL="2"/>
</networkConnectors>
Have also tried the simpler full duplex version with similar results.
And I have unique broker names.
If I now add a subscription on each of the 3 nodes to a topic /topic/foo and
send a message then I will get duplicates delivered to some of the
subscribers.
so my question is:
a) is this kind of thing possible, can I create meshes with routing loops
b) whats the right way?
--
View this message in context:
http://old.nabble.com/Correct-way-to-build-a-mesh-of-brokers-tp29255162p29255162.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
