[ https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633159#comment-14633159 ]
Alexander Lomov commented on CAMEL-8971: ---------------------------------------- As I see the only thing the patch does is disabling recovery despite of the RecoverableAggregationRepository settings. I believe it's not the desired solution. I've noticed LevelDBAggregationRepository in your tests fails to confirm an exchange is done. I guess it's the problem. > HazelcastAggregatorRepository redelivers incorrectly > ---------------------------------------------------- > > Key: CAMEL-8971 > URL: https://issues.apache.org/jira/browse/CAMEL-8971 > Project: Camel > Issue Type: Bug > Components: camel-hazelcast > Affects Versions: 2.16 > Reporter: Ben O'Day > Assignee: Ben O'Day > Priority: Minor > Attachments: HazelcastAggRepo-redelivery-fix.patch > > > seeing an incorrect redelivery of a message when using the > UseLatestAggregationStrategy... > this very basic route (see attached)... > from("direct:start") > .aggregate(constant(true), new > UseLatestAggregationStrategy()) > .completionSize(2) > > .aggregationRepository(repo) > .to("mock:mock"); > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)