You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Marco Crivellaro <ma...@gmail.com> on 2012/07/06 16:41:06 UTC
Aggregator Exchange.MULTICAST_COMPLETE recipientList
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
ENDPOINT2,ENDPOINT3,ENDPOINT1
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?
--
View this message in context: http://camel.465427.n5.nabble.com/Aggregator-Exchange-MULTICAST-COMPLETE-recipientList-tp5715630.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Aggregator Exchange.MULTICAST_COMPLETE recipientList
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, Jul 6, 2012 at 4:41 PM, Marco Crivellaro <ma...@gmail.com> 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
> ENDPOINT2,ENDPOINT3,ENDPOINT1
>
> 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: http://camel.465427.n5.nabble.com/Aggregator-Exchange-MULTICAST-COMPLETE-recipientList-tp5715630.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen