On Thu, Aug 27, 2009 at 5:10 PM, vezee<arun.addepa...@yahoo.com> wrote: > > > Its been a while since the below post. So, i have a Qn in regards to > Master-Slave clustering: > > Is fail-back still an issue in Master-Slave clustering? Any idea when its > gonna be fixed?
There is currently no fail-back feature in ActiveMQ. This is a very complex solution which is why it hasn't been created. > Clustering using Shared (FS/DB) seems to be the only solution at this moment > and is not a great idea for implementation for cross network or multi-data > center implementation. > > I am not sure, but there's something surely missing somewhere: > > 1. I bought the ActiveMQ in Action E-book yesterday (8/27/2009) and the > chapter related to CLUSTERING is missing or rather not yet WRITTEN!! (why?) The book is part of the Manning Early Release Program (MEAP) and is not yet complete. As we write the book, we continue to push updates to those who have purchased the book. The chapter on clustering was not yet complete enough to include in the last MEAP update. > 2. Since FUSE is also based on AMQ, i downloaded their doc.zip file and even > there there is no reference to CLUSTERING. Also, the docs shows "Admin > guide" in the index but the actual chapter is MISSING!! No idea, I haven't worked there in over a year. > If anyone knows, please share with us. We cannot even think of implementing > AMQ (or FUSE) in our org if it does not support proper industry standard > clustering mechanism. The master/slave features in ActiveMQ are for failover functionality. The network of broker features are for clustering/federation: http://activemq.apache.org/networks-of-brokers.html A network of brokers allows for broker-to-broker messaging based on demand from consumers subscribed to destinations. This is sometimes known as distributed queues. Bruce -- perl -e 'print unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
