activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Verhoeff <Stefan.Verho...@tomtom.com>
Subject Re: Receiving old messages on durable topics after application restart using ActiveMQ two node cluster
Date Tue, 10 Nov 2009 13:19:33 GMT

To work around the problem we decided to re-architect to use Queues instead
of Topics (since this application is the only one using Topics). The Virtual
Destinations page does look promising to provide a solution, thanks for the
advice.

Regards,
Stefan


Joe Fernandez wrote:
> 
> I have noticed the same thing. If your failover connector includes the two
> nodes, then it is likely that your application - as a result of restarts -
> has pollinated both brokers with the same durable subscription. However,
> within the context of the network of brokers, they are viewed as different
> durable subscriptions for the same topic? I tried setting 'dynamicOnly' to
> 'true', but that did not make a difference.  You can cut down on the
> liklihood of pollinating both brokers by setting 'randomize' to 'false'.
> This would force your consumer to always connect to the first broker on
> the list. Another option is to use 'virtual topics' in combination with
> 'dynamicOnly' being set to 'true'.
> 
> http://activemq.apache.org/virtual-destinations.html
> 
> Joe
> http://www.ttmsolutions.com  
> 

-- 
View this message in context: http://old.nabble.com/Receiving-old-messages-on-durable-topics-after-application-restart-using-ActiveMQ-two-node-cluster-tp26230816p26283278.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message