camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Aggregator Exchange.MULTICAST_COMPLETE recipientList
Date Fri, 06 Jul 2012 14:43:23 GMT
On Fri, Jul 6, 2012 at 4:41 PM, Marco Crivellaro <> wrote:
> Hi,
> I am currently using a recipientList with parallel processing and streaming
> option with a custom aggregator strategy.
> Exchange.MULTICAST_COMPLETE property read on aggregation seems to rely on
> the recipient list order instead of the order in which they are aggregated.
> For instance if in recipient list there are ENDPOINT1,ENDPOINT2,ENDPOINT3
> and they complete processing (hits aggregator)in following order
> the property Exchange.MULTICAST_COMPLETE on each exchange (newExhange param)
> will be populated as
> false,true,false same is for Exchange.MULTICAST_INDEX.
> Is there a built in way to know which is the last aggregation exchange in
> such situation?

No because you use parallel so the order can be random. You would need
to count the number of times you have aggregated and compare with the
SIZE property. Then you know its the last one.

> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message