Thanks MichaelAndrePearce. we will take a look at it
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
Thanks for the response art.
Yes we did an RCA and found out that the corruption was caused due to abrupt
termination of the broker. Be that as it may we were wondering if there was
an architecture that we can adapt that would be resilient to such scenarios.
But your argument makes sense.
We
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