You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/06/26 12:26:00 UTC

[jira] [Comment Edited] (CAMEL-15197) Thread pools in EIPs allow to use vertx thread pool instead

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

Claus Ibsen edited comment on CAMEL-15197 at 6/26/20, 12:25 PM:
----------------------------------------------------------------

We may want to introduce a simpler ThreadPoolFactory that can use a more basic ExecutorService SPI that only has the API we need for EIPs in Camel to use. We essentially only use submit(runnable) today.

And then we have some threads that should run in its own thread, such as when shutting down, we setup a background thread etc. So some API abstract for this.




was (Author: davsclaus):
We may want to introduce a simpler ThreadPoolFactort that can use a more basic ExecutorService SPI that only has the API we need for EIPs in Camel to use. We essentially only use submit(runnable) today.

And then we have some threads that should run in its own thread, such as when shutting down, we setup a background thread etc. So some API abstract for this.



> Thread pools in EIPs allow to use vertx thread pool instead
> -----------------------------------------------------------
>
>                 Key: CAMEL-15197
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15197
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, camel-vertx
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.x
>
>
> When using thread pools for EIPs like splitter, aggregator etc. We can make it possible to use external thread pool from vertx and its set of worker pools. For example with quarkurs or vertx this makes Camel work more naturally there using its existing threading model.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)