[
https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894322#comment-15894322
]
Claus Ibsen commented on CAMEL-8971:
------------------------------------
The aggregation strategy should favor returning the oldExchange - we had an
issue in the jdbc repo. Now Camel logs a WARN if you return the wrong instance.
> 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.14.1
> Reporter: 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.15#6346)
