[
https://issues.apache.org/jira/browse/AMQ-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004106#comment-14004106
]
Edwin Yu edited comment on AMQ-5196 at 5/21/14 10:34 PM:
---------------------------------------------------------
If you need my kahaDB folder from our master node to debug, I'd be glad to give
you a copy. It's 11GB big.
was (Author: windeyu):
If you need my kahaDB folder from our master node to debug, I'd be gladly give
you a copy. It's 11GB big.
> Corrupted Kahadb store after failover: "Could not load journal record.
> Invalid location"
> ----------------------------------------------------------------------------------------
>
> Key: AMQ-5196
> URL: https://issues.apache.org/jira/browse/AMQ-5196
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Message Store
> Affects Versions: 5.9.0
> Environment: Windows 7.
> <persistenceAdapter>
> <kahaDB directory="\\some.network.lan\amq"
> ignoreMissingJournalfiles="true" checksumJournalFiles="true"
> checkForCorruptJournalFiles="true"/>
> </persistenceAdapter>
> Reporter: Edwin Yu
> Attachments: masterNode.log, slaveNode.log
>
>
> I'm not sure if I can reproduce it, but it's important for me to report. We
> have a master/slave setup sharing the kahaDB store on a distributed network
> drive. The running master encountered some intermittent network issue for
> ten minutes or so, and finally invoked my DefaultIOExceptionHandler, which
> shut down the JVM. The slave took over and started up. All remote consumers
> reconnected to the slave node via the failover protocol. However, the slave
> node repeatedly complained about "Could not load journal record. Invalid
> location". All consumers were idle and didn't process any messages. Logs
> from both nodes are attached.
> We're running ActiveMQ 5.9.0. I copied over the kabadb folder to the latest
> ActiveMQ 5.9.1 where I also set ignoreMissingJournalfiles="true"
> checksumJournalFiles="true" checkForCorruptJournalFiles="true". It started
> up with the same error. It indicated to me that 5.9.1 cannot recover from
> the corrupted store either.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
