On Tue, Sep 15, 2009 at 3:21 PM, Julien D <[email protected]> wrote: > > Hi, > > I have a simple route which consums files from a directory. When I stop my > fileConsumer from Jconsole calling the stop method, the thread doesn't > disappear in the thread tab. When I re-start my consumer using the start > method another thread is created and the previous thread is still there > hanging. When I look into the code I can't see any call to the shutdown > method of the executor like in the jmsConsumer. > > Is this issue already known ?
Its again the JDK that handles the threads by the ExecutorService. However we do have on the roadmap to improve the configuration and management of this in Camel 2.1/2.2 or whenever we get the chance. As the file consumer is based on the scheduled polling consumer, it does in fact just "cancel" the task when its stopped. And thus the executor service is not shutdown. The issue is that it really could be a shared executor service (old design). which we have to overhaul later so you can better manage this. > > Regards > > Julien > -- > View this message in context: > http://www.nabble.com/Camel-file-tp25453920p25453920.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
