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-3576) camel-jms - Provided a task executor by default
Date Sun, 06 Feb 2011 15:24:30 GMT

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

Claus Ibsen commented on CAMEL-3576:
------------------------------------

trunk: 1067682.

Don't use thread pool for single threaded reply manager as Spring DMLC is a bit pants as it
will keep using new tasks every second when idle, and that just confuses people, as task count
will grow very large.

> camel-jms - Provided a task executor by default
> -----------------------------------------------
>
>                 Key: CAMEL-3576
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3576
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.7.0
>
>
> When using camel-jms the consumers dont provide a default task executor. That means spring
just creates a thread manually and dont reuse the thread.
> We should provided a task executor from camel using the ExecutorServiceStrategy. This
allows us to use human readable thread names which can provide details about the consumer.
The thread pool is also managed and even a 3rd party provider can manage thread creation.
> This only works when using Spring 3 as the task executor API is now aligned with the
executor service api from the JDK.
> For Spring 2.x users we should not do this. We will then have to detect the spring version
in use.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message