This is interesting. When i use a purposefully slow set of 3 brokers sharing an NFS 4 mount, I found that it's very very easy to get them into a bad state.
As simple a procedure as starting them in sequence and then restarting them in the same sequence nets me errors like: 2016-02-29 19:17:46,218 [erSimpleAppMain] INFO Journal - Corrupt journal records found in '/var/log/activemq/activemq-data/amq-dev-2/db-1.log' between offsets: 832..903 2016-02-29 19:17:46,219 [erSimpleAppMain] INFO Journal - Corrupt journal records found in '/var/log/activemq/activemq-data/amq-dev-2/db-1.log' between offsets: 3687 2016-02-29 19:17:46,219 [erSimpleAppMain] INFO Journal - Corrupt journal records found in '/var/log/activemq/activemq-data/amq-dev-2/db-1.log' between offsets: 3688..3805 2016-02-29 19:17:46,231 [erSimpleAppMain] INFO Journal - Corrupt journal records found in '/var/log/activemq/activemq-data/amq-dev-2/db-1.log' between offsets: 4711..4757 I'm going to try again w/o the latency, but so far this isn't any more promising than the buggy zookeeper code. Jim
