camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1588) ExecutorService configuration
Date Fri, 04 Dec 2009 12:35:52 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56258#action_56258
] 

Claus Ibsen commented on CAMEL-1588:
------------------------------------

Supports thread pools using core pool size, max pool size, timeout etc.

e.g. we gotta do this ourself instead of the pre existing on the Executors.

{code}
 ExecutorService executor = new ThreadPoolExecutor(numberOfThreads, numberOfThreads, 60, TimeUnit.SECONDS,
new LinkedBlockingQueue<Runnable>());
{code}

This can be retrofitted in the ExecutorServiceHelper which camel uses to obtain a default
pool.

> ExecutorService configuration
> -----------------------------
>
>                 Key: CAMEL-1588
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1588
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.0-M1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.2.0
>
>
> Camel uses some thread pools, for component, endpoint and processor.
> We should have some default configuration that is easy to configure with Camel to adjust
pool sizes for individual/groups/type etc.
> By not they use 5 as the default pool size. And have their own executor unless configured
otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message