there are quite a few issues backing up against the pure master slave (nothing shared) support, as a feature, it is not getting much love. Most folks use a shared file system or shared db, so shared store setup so that is where most of the work is focused. A 2 broker network can give your producers some level of fault tolerance, but total order of messages will be lost and any messages pending on a failed broker will remain there till it is restarted. Best a network of shared store master/slave pairs
On 8 September 2011 13:05, dcheckoway <[email protected]> wrote: > Torsten/Gary, > > This (thread) talks about the master/slave issue I made reference to > earlier... > > ----- > Dan Checkoway > dcheckoway gmail com > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Slave-not-replicating-consumption-with-Pure-Master-Slave-tp3767086p3798603.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://fusesource.com http://blog.garytully.com
