Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Unknown
Description
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.