Try this: ActiveMQ v5.5.1 Corrupt data log found recovery: Symptom: The ActiveMQ slave process died and will not restarted.
Root Cause: Corrupt data log found Root Cause verification: Search the affected ActiveMQ log file for the following entries in sequence: Corrupt journal records found Failed to discard data file Failed to start ActiveMQ JMS Message Broker shutting down Recovery: Shutdown the ActiveMQ master instance. Rename the Kaha db storage file Restart the ActiveMQ Master and Slave instances Note: the journal data affected by the corruption will be lost. The affected journal data will need to be identify and resent to the ActiveMQ appropriate queue. -- View this message in context: http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p4668099.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
