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: http://camel.465427.n5.nabble.com/Aggregator-and-HawtDB-DB-just-seem-to-grow-tp5576730p5576730.html Sent from the Camel - Users mailing list archive at Nabble.com.
