camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Aggregator and HawtDB - DB just seem to grow?
Date Mon, 19 Mar 2012 11:20:15 GMT
What version of hawtdb and Camel are you using?

There was a bug a while back, that caused it to grow. That was fixed
in a recent release of hawtdb.

On Mon, Mar 19, 2012 at 12:06 PM, mikaelfj <> wrote:
> Hi,
> We are using the aggregator EIP to collect a set of files from which we are
> to generate other documents.
> In order not to loose any of the aggregated documents, we are using the
> aggregator with the HawtDB as aggregation-repository.
> This has been running flawless for a few months, but two weeks ago we
> suddenly began getting:
> org.fusesource.hawtdb.api.IOPagingException: Invalid extent read request.
> The requested page was not an extent: xxxx
> This was "fixed" by extending the buffersize from the default 8Mb to 32Mb.
> Now the problem has arisen again and we have the same kind of exceptions in
> the logs.
> None of the file sets that are read are very big in size, so it is unlikely
> that a single file set would cause the HawtDB to go pass its limit.
> Can it be that the HawtDB just grows?
> ... or did I miss something in the configuration of the route?
> When reading the documentation in "The Book" it says that the Aggregator
> will issue a Commit, when the message has been processed successfully. This
> will cause the RecoverableAggregationRepository to Confirm the message, thus
> ensuring it will not be recovered.
> But, will the Confirm remove the message or do I have to perform a cleanup
> of successfully processed messages in order to keep the HawtDB from growing?
> Best regards
> Mikael
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
CamelOne 2012 Conference, May 15-16, 2012:
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message