I am also getting this issue on 5.4.1. Is it resolved in a later release?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Kaha-corruption-in-5-4-SNAPSHOT-tp2366036p3450835.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I'm getting the same issue with the release version of 5.4.0. Deleting the
db.data avoids the problem, however, I would like to have the recovery
happen automatically without having to manually delete this file. Is there
a way to achieve this?
ripienaar wrote:
>
>
>
> Gary Tully wrote:
>>
>>
Gary Tully wrote:
>
> your understanding is correct, If you delete the index, db.data, it
> should be able to recover the index by replaying the journal and
> recreating the index from scratch.
> If that does not work, can you please open a jira issue and attach
> your test case or configuratio
your understanding is correct, If you delete the index, db.data, it
should be able to recover the index by replaying the journal and
recreating the index from scratch.
If that does not work, can you please open a jira issue and attach
your test case or configuration setup and the relevant logs. Als
