If you haven't done so already, consider using virtual topics. It gives you the functionality of durable topics plus the added benefits of queues. If you find that virtual topics meet your requirements, I'd recommend setting the network connector option, 'dynamicOnly' to true. This ensures that a broker does not forward a message to another broker with a 'non-active' consumer, as described in your posting.
http://activemq.apache.org/virtual-destinations.html Joe Podloucky Konrad wrote: > > Hi there, > > I am currently evaluating ActiveMQ for use in a distributed network > (hub/spoke topology). We have to deal with unreliable connections, so > failover for clients is pretty much desired. > > I have noticed the following behaviour while testing durable subscribers > (Version is 5.0.0): > > As long as the durable subscriber always connects to the same broker > there is no problem, messages are routed as expected. However, as soon > as the subscriber connects to a different broker, messages queued for > the subscriber on the original broker are not forwarded to the consumer > and new messages are now sent to both brokers. > > I realize this is a tricky situation, but is this intended behaviour? If > yes, I would have to make sure that durable subscribers are only > registered at one broker at a time to keep messages from queueing up on > one broker which will never be consumed. > > Cheers, > > Konrad Podloucky > > > ------------------------------------------------- > Sitz: Wien, FG: Handelsgericht Wien, FN: 189025 d > > > > -- View this message in context: http://www.nabble.com/Network-of-Brokers-and-Durable-Subscribers-tp14663184s2354p14675966.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
