[
https://issues.apache.org/jira/browse/CAMEL-17014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17014:
--------------------------------
Fix Version/s: 4.0
(was: 3.x)
> camel-core - SPI for shared Camel worker thread pool
> ----------------------------------------------------
>
> Key: CAMEL-17014
> URL: https://issues.apache.org/jira/browse/CAMEL-17014
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.0
>
>
> Some components have their own thread pool for worker threads that they use.
> For example salesforce, kafka, jms, and others.
> They use this continue routing in Camel when the component has received a
> response or ack from the underlying 3rd party (kafka, jms, salesforce etc.)
> We should consider a API with a SPI so we can use a shared worker pool from
> camel-core that has a fixed set of worker threads. Then its easier to control
> total number of threads / pools etc.
> And with a SPI then we can delegate this to another runtime such as vertx,
> quarkus etc that has such concept.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
