Hello,
i've found a workaround.
It looks like that the instance of the ExecutorService and Splitter are
stored in the model (RouteDefinition).
So everything works fine if i create a new instance of the
RouteDefinition. But i think it should be fixed for consistency
(Aggregator and AggregatorRepository are not stored in the model)
Hi,
I am running multiple Camel instances in the same JVM. Each Camel
instance should have an unique, custom Executerservice. I set the
Executerservice to the CamelContext registry.
But when i start the same route in two different contexts, the
executerservice gets shared.... (Same issue with a custom splitter)
How can i avoid this?
Thanks,
Stefan
