On Fri, Mar 9, 2012 at 10:50 AM, Aida <[email protected]> wrote: > Hi Claus, > > This is quite weird but calling ”camelContext.removeEndpoints(endpointUri)” > has no effect, the threads still there (from now, the inmortal thread, ;-D) >
Can you try to stop the endpoint before removing it. Also see CAMEL-4976 as there may was a problem with this. > Furthermore, if I call “camelContext.getEndpoints()” these endpoints are not > in the list. > Instead of using different endpoints all the time. You can use the same endpoint. And then use a filter class, where you in the filter class can check if you accept the file or not. Also see this FAQ http://camel.apache.org/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.html > If it helps, I am using a spring based camel context. > > Moreover, I see that the GenericFileEndpoint are “not lenient” by default > (line 326 in DefaultEnpoint) so when I get the endpoint key, the properties > (filename among others) are used to create the key, so I always get a > different endpoint for each file read, isn’t it? > > Thanks again for your time > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/FTP-ConsumerTemplate-Threads-remaining-alive-tp5548338p5550086.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
