Page History

...

It should be possible to configure a thread pool on either per CamelContext level or per Route level, such as you can do with AutoStartup and the likes.
Then you can say, eg this route should use this pool, which have 20/50 in the pool size etc. IN PROGRESS CHANGE OF PLAN

Thread pool configuration by rules

It should be possible to to define a set of rules which matches which thread pool a given source should use.
It should be pattern based so you can say all EIPs should use this pool, all endpoints that pool etc.

A ruleset something like this:

<threadPoolRule route="*" source="Aggregator" executorServiceRef="myAggPool"/>
<threadPoolRule route="*" source="To" executorServiceRef="mySendPool"/>
<threadPoolRule route="route3" source="*" executorServiceRef="myRoute3Pool"/>

Where it will match against route first, so if we got a route3 then it will pick among those
It should be possible to use wildcard and reg exp in the route and source attributes.

The problem with shutdown and restarting pools

...