Hi Each component has a setExecutorService where you can inject the ThreadPool.
But I dont think you can set it on the CamelContext so every component will default use the one you have defined. But its a good idea if you for instance runs in a managed environment such as WebSphere where you can define thread pools. There was a topic on this user forum about the WebSphere stuff recently. Try search a little. And feel free to create a ticket in JIRA for the configuration of the executor service on CamelContext. Have I missed something? Maybe you can do something smart with Spring and have it autowired? On Wed, Jan 14, 2009 at 9:32 AM, Manish K Bafna <manish.ba...@headstrong.com> wrote: > Hello, > Is there a way to provide a Thread pool to the camel context so that threads > of the polling consumers can be managed? Right now, every polling consumer is > running on a different threads and therefore if there are many routes, many > threads are created. > > Thanks, > Manish. > > > > ***The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review,retransmission,dissemination or other use of, or taking > of any action in reliance upon, this information by persons or entities other > than the intended recipient is prohibited. If you received this in error, > please contact the sender and delete the material from any computer.*** > -- /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/
