You said the broker still held the file lock, but I assumed that the broker process exited without releasing the lock (since it couldn't write to disk). Can you confirm that the master broker process really was still running (as seen by ps, not just the state of the file lock)?
If the broker process really was still running, the problem is actually that the broker tries to shutdown but fails to do that when the broker can't write to the disk that hosts KahaDB. If the process exited but the disk still thinks the master broker holds the lock because it couldn't write to disk to release the lock, then the problem is that the slave broker isn't able to detect that the master exited without releasing the lock. Your JIRA should be updated in either case, but you need to know whether the process exited to know which update to make. On Jan 27, 2015 11:20 PM, "khandelwalanuj" <[email protected]> wrote: > Hi, > > Master was not completely killed. Master has stopped it's transport > connectors and plugins but it didn't release it's lock from the kahadb. > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException-Input-output-error-tp4690378p4690514.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
