activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SuperOook <fuhrmann.ha...@scheidt-bachmann-st.de>
Subject Limitations for global topics in a ring of brokers
Date Thu, 18 Feb 2016 07:12:15 GMT
Hi there,

what are the exact limitations of topics which are spread over a cluster of
brokers? I want to use a mesh- or ring-topology with potentially quite a few
brokers (~10-150).

The wiki says [1] 

Distributed Topics in Store/Forward
For topics the above algorithm is followed except, every interested client
receives a copy of the message - plus ActiveMQ will check for loops (to
avoid a message flowing infinitely around a ring of brokers).

What exactly does "will check for loops" mean? Will ActiveMQ still allow and
correctly handle distributed topics when there are loops in the network? Or
will it just somehow abort and not allow to use distributed topics when
there are loops? The latter is the case for some other JMS implementations I
used, e.g. the Tibc* EMS; which is quite a strong limitation. Any other
limitations? Maybe about durable topics in a looped cluster?

Is there any further documentation about handling of loops available? I
found some nice explanations with RH A-MQ about self-avoiding paths [2] or
the different topologies [3]. However, the text about self-avoiding paths
only explicitly addresses Queues.

Cheers,
Hauke


[1] http://activemq.apache.org/how-do-distributed-queues-work.html
[2]
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_A-MQ/6.2/html/Using_Networks_of_Brokers/FMQNetworksMessagePropagation.html
[3]
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_A-MQ/6.2/html/Using_Networks_of_Brokers/FMQNetworksTopologies.html



--
View this message in context: http://activemq.2283324.n4.nabble.com/Limitations-for-global-topics-in-a-ring-of-brokers-tp4707717.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message