camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Autric <>
Subject Re: Camel quartz memory leak
Date Thu, 13 Aug 2015 13:33:19 GMT
Hi Akram,

feel free to rise a JIRA ticket (
And create an PR to github (

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:
Le Linea, 1 rue du General Leclerc, 92047 Paris La Défense Cedex
Sent from webmail

----- Mail original -----
De: "Akram" <>
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..

    public void shutdown() throws SchedulerException, InterruptedException {
        Scheduler scheduler = super.getScheduler();
        if (scheduler != null) {
            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:
Sent from the Camel - Users mailing list archive at

View raw message