You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Alexander Lomov (JIRA)" <ji...@apache.org> on 2015/07/15 12:38:04 UTC
[jira] [Commented] (CAMEL-8971) HazelcastAggregatorRepository
redelivers incorrectly
[ https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627867#comment-14627867 ]
Alexander Lomov commented on CAMEL-8971:
----------------------------------------
Will check, Ben.
> 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)