What is the best architecture to set up an activemq cluster to achieve high service and data availability
We are currently in the process of setting up a highly available active-mq
cluster that has 1 master and 2 slave nodes that share the same file system.
However we felt this architecture might not be a safe from issues such as
kahadb corruption. We recently faced an issue where the only way to start up
the broker was to delete all the kahadb data as it never successfully
So our question is whether we can opt for a setup that is both highly
available service wise but also replicates the data in the background so
that we can recover the data from a secondary node when there is a
corruption of data in the primary storage node. Does active-mq support an
architecture such as that?
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html