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 2011/10/04 18:00:04 UTC
RecipientList-AggregateTask thread creation
I have a route with a recipientList parallel processed and than streamed to
an aggregation strategy:
.recipientList(header("recipientListHeader").tokenize(","))
.parallelProcessing().timeout(30000)
.executorService(customThreadPoolExecutor)
.streaming().aggregationStrategy(new
RecipientAggregationStrategy()).to("direct:chunk.completed");
most of the times the thread used for RecipientAggregationStrategy is the
same through several exchanges hitting the recipienList but from time to
time a new thread is created. I cannot identify any pattern which might
cause a new thread to be created. Can you please explain how camel decides
if a new thread has to be allocated? Will any previous thread be killed?
--
View this message in context: http://camel.465427.n5.nabble.com/RecipientList-AggregateTask-thread-creation-tp4869248p4869248.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: RecipientList-AggregateTask thread creation
Posted by Claus Ibsen <cl...@gmail.com>.
Its the JDK that allocated threads from the thread pool to execute the
tasks from the work queue.
See also details here
http://camel.apache.org/threading-model.html
On Tue, Oct 4, 2011 at 6:00 PM, Marco Crivellaro <ma...@gmail.com> wrote:
> I have a route with a recipientList parallel processed and than streamed to
> an aggregation strategy:
>
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing().timeout(30000)
> .executorService(customThreadPoolExecutor)
> .streaming().aggregationStrategy(new
> RecipientAggregationStrategy()).to("direct:chunk.completed");
>
>
> most of the times the thread used for RecipientAggregationStrategy is the
> same through several exchanges hitting the recipienList but from time to
> time a new thread is created. I cannot identify any pattern which might
> cause a new thread to be created. Can you please explain how camel decides
> if a new thread has to be allocated? Will any previous thread be killed?
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/RecipientList-AggregateTask-thread-creation-tp4869248p4869248.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.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/