Hi Akram, feel free to rise a JIRA ticket (https://issues.apache.org/jira/browse/CAMEL) And create an PR to github (https://github.com/apache/camel)
Camel commiters will analyse it, and accept it if it is confirmed issue. thx for your help, Greg AUTRIC JBoss Middleware Consultant email : gautric __at__ redhat __dot__ com twitter : @gautric_io Red Hat Global Services Red Hat France SARL sit: http://www.redhat.fr Le Linea, 1 rue du General Leclerc, 92047 Paris La Défense Cedex Sent from webmail ----- Mail original ----- De: "Akram" <akram.s...@gmail.com> À: users@camel.apache.org Envoyé: Mercredi 12 Août 2015 23:11:41 Objet: Re: Camel quartz memory leak I have resolved the issue.. It is an issue with quartz component. Quartz was being shutdown but the webapp didn't wait for quartz to finish before it shutdown so Tomcat decided that it had left threads running and complained. So, i override the shutdown method in quartzcomponent as follows and it worked for me.. @Override public void shutdown() throws SchedulerException, InterruptedException { Scheduler scheduler = super.getScheduler(); if (scheduler != null) { scheduler.shutdown(true); Thread.sleep(1000); scheduler = null; } } Note the boolean argument to shutdown is the vital part. If you remove that true to call the no-arg version or set it to false, your webapp won't wait for quartz to shudown before it shuts down. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5770634.html Sent from the Camel - Users mailing list archive at Nabble.com.
