For active deployments (all brokers active in your cluster), you'll won't be able to share databases. You could try out network of brokers for clustering where all brokers are active, connected to each other, etc, but they would all have their own persistence stores.
On Thu, Jun 20, 2013 at 6:29 AM, deepak_a <angesh...@gmail.com> wrote: > As per this link > http://activemq.apache.org/can-two-brokers-share-the-same-database.html > > It appears the recommendation is not to share database. > > This link recommends another strategy > http://activemq.apache.org/jdbc-master-slave.html > But this will work if I were to follow "Clustered Singleton Services" i.e. > a > Master node in my cluster runs and if it goes down, one of the other nodes > resumes. > > But my strategy is to use "Farming Deployment" where all nodes will be up > and running and processing messages and each node will have an activeMQ > broker (but the database being shared) > > Would appreciate if some one can suggest some ideas. > > > regards > D > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/activeMQ-clustering-integrated-with-JBoss-tp4668358p4668408.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
