hmm, ActiveMQ should satisfy your requirement in this area. Have a peek at org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest[1]
and see if you can make a variant that validates your restart broker scenario. This will be the best way to capture your requirement and also can provide the input for a jira issue if necessary and provides something of value that we can add to the ever growing cohort in use cases in activemq-core [1] https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriberWithNetworkDisconnectTest.java On 20 March 2012 15:12, john.horner <john.hor...@openroadsconsulting.com> wrote: > Thank you for the rapid response. I have changed my network connector > definition to the following: > > > > and I still get the same behavior as before. Fault tolerance for broker > failure is a critical requirement for us. Please help me understand a > couple of things about this. > > > Is ActiveMQ intended to satisfy the use case in my original post (messages > automatically start flowing to durable subscribers upon restart of a failed > broker)? > > If the answer to the above is 'yes', then is it worth my exploring whether a > previous version has a different behavior than what I'm currently seeing? > > Thanks very much for your assistance. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/durable-consumers-and-broker-failure-tp4486347p4489140.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
