[
https://issues.apache.org/activemq/browse/CAMEL-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47880#action_47880
]
tim mcnamara commented on CAMEL-1098:
-------------------------------------
The unfortunate issue here is that there is another API (Timer) that
provides the equivalent to ScheduledExecutorService. This API is
significantly different to the Java SE concurrent equivalents that
would make the previous approach of proxying the interfaces very
difficult. So for now, it looks like there is no clean way to use
ScheduledExecutorService implementations in a managed environment.
Moving forward, my suggestion would be for Camel to have it's own
abstraction, similar to Spring's TaskExecutor, that would allow for
the configuration of thread management whether running in a managed
container or not.
JSR 236 offers hope for the future.
Tim...
> multicast and file consumer using managed threads?
> --------------------------------------------------
>
> Key: CAMEL-1098
> URL: https://issues.apache.org/activemq/browse/CAMEL-1098
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.4.0, 1.5.0
> Reporter: tim mcnamara
> Assignee: Willem Jiang
> Fix For: 2.0.0
>
> Attachments: executor.patch, multicast.patch
>
>
> Running in a server managed environment, it is preferable to use managed
> threads when ever possible. Is it possible to have these components (and
> others that spawn threads) modified to use Spring's TaskExecutor abstraction
> (a la JmsComponent). If this is the case, we could configure the components
> to use the server's WorkManager API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
