camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: How to recover corrupted HawtDB files
Date Tue, 16 Jul 2013 21:22:36 GMT
I'm not sure whether this is the best forum for this kind of question. May
be posting on the HawtDB mailing list makes more sense...

Only my 0,02 €,
Christian
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Tue, Jul 16, 2013 at 10:12 AM, Stefan Burkard <sburkard@gmail.com> wrote:

> Hi Camel users
>
> I have a component with 2 persistent aggregators. One receives all
> messages, one only a part of them. After a lot of test runs without
> problems I had yesterday a serious problem with the aggregator persistence
> (hawtdb).
>
> I don't know yet what causes the problems, but however, problems can
> occur. My problem is that I cannot recover the data from the hawtdb-files.
>
> Im my logs, I got first of all about 8 stacktraces like the attached
> "stacktrace1.txt". The number in the error message "The requested page was
> not an extent: 35" is growing from stacktrace to stacktrace from 35 to 1163.
>
> Then, I got some stacktraces like the attached "stacktrace2.txt".
>
> Finally I got A LOT of stacktraces like the attached "stacktrace3.txt".
>
> After shutting down the component gracefully, I tried to restart it, but
> this throws stacktraces like the attached "stacktrace-startup.txt".
>
> I can only start the component again if I rename the hawtdb-files so they
> are ignored and new hawtdb-files are created.
>
> This leaves me with the question: how can I recover the corrupted
> hawtdb-files? I didn't found anything about this subject and if this is not
> possible, this would be a real show-stopper.
>
> Thanks for any help
> Stefan
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message