camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: Quartz job data deletion in clustered quartz2
Date Fri, 21 Nov 2014 08:38:28 GMT
camel-quartz component is managed the scheduler rightly if the scheduler is created by itself.
But it is not his job to clean up job data if the scheduler is created from outside.

Quartz scheduler should be more resilient by keeping processing other triggers as you suggested.

Willem Jiang

Red Hat, Inc.
Blog: (English) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem

On November 21, 2014 at 4:07:24 PM, lakshmi.prashant ( wrote:
> Hi Willem,
> We are listening to the un-deployment event ourselves.
> 1. Actually, if the job is deleted from any UI (that is used to schedule
> jobs) - that UI will have to take care to remove the job data from the
> scheduler.
> 2. But, in the camel quartz scenarios, the jobs are created at the start of
> routes. Once the routes get removed (un-deployed), the quartz Job data will
> also have to be removed.
> Quartz scheduler will not automatically come to know of this. I had
> already raised an issue in quartz forum that they should make some
> improvement:
> (i.e.) Quartz scheduler has to handle the following situation while
> acquiring triggers to be run: if the job class related to any job is
> missing, it should remove that job data (or) log the issue & ignore that &
> continue processing the other triggers.
> 3. Unless the issue is resolved either in camel or in quartz, users of
> clustered camel quartz will continue to face this issue, as all camel quartz
> routes will stop running.
> Thanks,
> Lakshmi
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

View raw message