The solution/workaround for us was to move away the 3 db.* files and let Kahadb
start with only the journal files.
It recreated the 'index' files and since then we're ok.
On 05.10.2016 14:48, Tim Bain wrote:
Martin Lichtin, did you ever resolve what was causing your problem, or how
to work
Martin Lichtin, did you ever resolve what was causing your problem, or how
to work around it?
Tim
On Sep 2, 2016 3:11 AM, "lichtin" wrote:
> I read through all release notes 5.13.x and 5.14.0 and cannot find a KahaDb
> incompatibility issue.
> This is quite an unexpected
I read through all release notes 5.13.x and 5.14.0 and cannot find a KahaDb
incompatibility issue.
This is quite an unexpected blocker for anyone trying to upgrade to 5.14.0.
Will try temporarily setting ignoreMissingJournalfiles=true and see it if
comes up, then later try changing it back.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/KahaDb-issue-Detected-missing-journal-files-when-upgrading-from-5-12-2-to-5-14-0-tp4716052p4716099.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Martin,
When updating from 5.11 to 5.14 I encountered a different issue (which might
have existed during earlier upgrades as well). I am in the situation that I can
remove the kahadb contents before starting 5.14. Maybe that can be a solution
for you as well.
Also see the thread