activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rodos77 <eugene.ro...@nexj.com>
Subject Re: Kaha corruption in 5.4-SNAPSHOT
Date Tue, 07 Sep 2010 23:45:35 GMT

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:
>> 
>> 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. Also if
>> you can share the data directory that cannot be recovered it would
>> help reproduce.
>> 
> 
> Thanks, I'll give it a go.
> 
> Is there a reason why recovery from journal isn't the default behavior
> when a broker starts and cant load its data?  This is in line with what
> most databases do so that unattended startups work.
> 

-- 
View this message in context: http://activemq.2283324.n4.nabble.com/Kaha-corruption-in-5-4-SNAPSHOT-tp2366036p2530590.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message