Actually, looking at the comments in the Camel code I wonder if I should
simply implement a custom ThreadPoolFactory rather than an
ExecutorServiceManager.
On Fri, Jun 22, 2018 at 6:52 PM Darius Cooper
wrote:
> Zoran, thanks for the great answer.
>
>
> I got it working by implementing a proof-of
Zoran, thanks for the great answer.
I got it working by implementing a proof-of-concept ExecutorServiceManager
and delegating all the methods that return either ExecutorService of
ScheduledExecutorService
Thinking about how this should look in production…
1. get/set ThreadPoolFactory: I assu
Hi Darius,
you need to implement ExecutorServiceManager[1] interface and delegate
to ExecutorService you looked up in Liberty and set that
implementation on CamelContext via setExecutorServiceManager[2]
method. If you're using Camel Spring XML support and
ExecutorServiceManager is available in the
The Camel In Action book says: "When you need to use a different thread
pool provider (for example, a provider from a Java EE server), you can
create a custom ExecutorServiceManager to work with the provider. "
On IBM Liberty, by turning on the feature "concurrent/1.0" one can get an
ExecutorServ
