Hi Ah <threadPool> and <threadPoolProfile> was intended for the EIPs, as there is special support for looking up when using EIPs and not when doing a endpoints.
We would need to add support for this in the EIPs from the default component. You are welcome to log a ticket. http://camel.apache.org/support On Wed, Jun 3, 2015 at 8:04 AM, Kondalarv <[email protected]> wrote: > Here is route information. > > file:/app/test/sat_data/tp/test1?readLock=changed&maxMessagesPerPoll=1&preMove=wip&initialDelay=3000&delay=3000&autoCreate=false&move=done/${date:now:yyyyMMdd}/${file:name}.${date:now:yyyyMMddhhmmss}&moveFailed=error&scheduledExecutorService=#filewatcherThreadPool > > Thread Pool information : > > <camel:camelContext xmlns="http://camel.apache.org/schema/spring";> > <contextScan/> > <threadPool id="filewatcherThreadPool" > threadName="filewatcherThreadPool" > poolSize="1" maxPoolSize="1" maxQueueSize="-1"/> > </camel:camelContext> > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/File-Component-scheduledExecutorService-throwing-Error-tp5767814p5767822.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
