On Fri, Jun 22, 2012 at 12:31 PM, Marco Crivellaro
<marco.cr...@gmail.com> wrote:
> Hi all,
> I am re-factoring a component which makes use of Camel (just moved to camel
> 2.9.2),
> a part of the route is currently built as:
>
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing().timeout(aggregationTimeout)
> .executorService(customThreadPoolExecutor)
> .streaming().aggregationStrategy(new
> RecipientAggregationStrategy(deliveryEndpoints, endpointDeliveredBaseUri))
> .to("direct:end");
>
> RecipientAggregationStrategy implements TimeoutAwareAggregationStrategy
> aggregationTimeout is currently a fixed (set at the start of the route), I
> would like to make it dynamic so I was thinking on using completionTimeout
> which supports dynamic value (from expression)
>
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing()
> .executorService(customThreadPoolExecutor)
> .streaming()
> .aggregationStrategy(new RecipientAggregationStrategy())
> .completionTimeout(1000)
> .to("direct:end")
>
> for some reason it doesn't accept completionTimeout, it seems it is uses
> recipientList definition instead of aggregation one.
> Is there a way I can change my route so that I can use a dynamic timeout?
> timeout from recipientList doesn't support expressions.
>
>No the timeout is fixed for recipient list. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/recipientList-aggregationStrategy-and-completionTimeout-tp5714917.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
