I'm using an the aggregator with the LevelDBAggregationRepository and seeing an incorrect redelivery of a message when using the UseLatestAggregationStrategy...
this very basic route (see attached)...
.aggregate(constant(true), new UseLatestAggregationStrategy())
shows the following behavior...
WARN LevelDBAggregationRepository - Unable to confirm exchangeId [ID-localhost-63819-1436483565832-0-6 from repository repo1: Not Found]
DEBUG LevelDBAggregationRepository - Scanned and found 1 exchange(s) to recover (note some of them may already be in progress).
DEBUG LevelDBAggregationRepository - Recovering exchangeId [ID-localhost-63819-1436483565832-0-3] -> Exchange[Message: test1]
resulting in a duplicate message being processed through the aggregator route...
if the default in-memory repo is used, the test behaves as expected...no unnecessary redelivery, etc.