Quartz Java resuming a job executes it many times

Question

For my application I create jobs and schedule them with CronTriggers. Each job has only one trigger and both the job name and the trigger names are the same. No jobs share a trigger.

Now when i create a cron trigger like this "0/1 * * * * ?" which instructs the job to execute every second, it works just fine.

The problem rises when I first pause the job by calling:

scheduler.pauseJob(jobName, jobGroup);

and then resuming the job after let's say 50 seconds with:

scheduler.resumeJob(jobName, jobGroup);

What I see is that for these 50 seconds the job did not execute as requested. But the moment I resume the job I see 50 executions of the job at the same time!!!

I thought that this was due to the default setting for the misfire instruction but even after setting the trigger's misfire instruction upon creation to this:

trigger.setMisfireInstruction(CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING);

The same thing happens. Can anyone suggest a way to fix this?

score 35 · Accepted Answer · edited Apr 21 '16 at 16:32

The CronTrigger works by remembering the nextFireTime. After creating the trigger the nextFireTime is initialized. Every time the job is triggered nextFireTime is updated. Since the job is not triggered when paused nextFireTime remains "old". So after you resume the job the trigger will return every old trigger time.

The problem is, the trigger doesn't know it is being paused. To overcome this there is this misfire handling. After resuming the jobs the trigger's updateAfterMisfire() method will be invoked which corrects the nextFireTime. But not if the difference between nextFireTime and now is smaller than the misfireThreshold. Then the method is never called. This threshold's default value is 60,000. Thus if your pause period would be longer than 60s everything would be fine.

Since you have problems I assume it is not. ;) To workaround this you can modify the threshold or use a simple wrapper around CronTrigger:

public class PauseAwareCronTrigger extends CronTrigger {
    // constructors you need go here

    @Override
    public Date getNextFireTime() {
        Date nextFireTime = super.getNextFireTime();
        if (nextFireTime.getTime() < System.currentTimeMillis()) {
            // next fire time after now
            nextFireTime = super.getFireTimeAfter(null);
            super.setNextFireTime(nextFireTime);
        }
        return nextFireTime;
    }
}

Thank you sooo much :) this worked like a charm. It seems weird that such a simple task as pausing a job would create problems like this. — Savvas Dalkitsis, Dec 28 '09 at 14:57

score 6 · Answer 2 · answered Dec 19 '09 at 18:05

6

If you pause the job, the trigger will continue to fire, but the executions will queue up until the job is resumed. This isn't a misfiring trigger, so that setting will have no effect.

What you want to do, I think, is programmatically disable or remove the cron trigger, rather than pausing the job. When you want to resume, then re-add the trigger.

answered Dec 19 '09 at 18:05

skaffman

398,947
96
818
769

1

The javadoc for the pauseJob method says "Pause the JobDetail with the given name - by pausing all of its current Triggers." so i am guessing the trigger is being paused. Also there is no pause method on the trigger itself. Or anything that resembles it. Is simply removing the trigger from the job and the reinserting it my only option to pause a job? I mean this is a pretty trivial thing to want your scheduler to do. How come it doesn't simply work? – Savvas Dalkitsis Dec 19 '09 at 18:08
Hmm, good point. I find that with Quartz, trying various things until something works is the most productive approach, since it doesn't always do what it says on the tin. – skaffman Dec 19 '09 at 18:13
This is extremely frustrating since there is also no easy way to simply remove a trigger from the job. Can i have a trigger-less job? and if yes, how? Any ideas? I'm starting to lose my patience with this, i have been trying for hours :) – Savvas Dalkitsis Dec 19 '09 at 18:18

score 1 · Answer 3 · answered Feb 14 '10 at 05:36

Since 1.6.5 at least (the earliest version of quartz at my fingertips), the scheduler has a pauseTrigger method that takes the name/group as parameters. This means you don't have to have a sub-class of every trigger type you use, nor do you have to do funky deletion/insertion tricks.

Both of these are important to me because 1) our database has a strict no-deletes policy and 2) the custom datastore I use doesn't support trigger sub-classes.

score 0 · Answer 4 · answered Apr 12 '21 at 08:28

you can add these code in org.quartz.impl.jdbcjobstore.JobStoreSupport#resumeTrigger(Connection conn, TriggerKey key)

OperableTrigger trigger = getDelegate().selectTrigger(conn, key);
if (trigger.getNextFireTime().getTime() < System.currentTimeMillis()) {
trigger.setNextFireTime(trigger.getFireTimeAfter(null));
}
JobDetail job = retrieveJob(conn, status.getJobKey());
storeTrigger(conn, trigger, job, true, status.getStatus(), false, false);

Using these code, when the paused job be resumed it will not be fired at once.On the other hand, it will be fired at next fire time which is calculated by resumed time

Quartz Java resuming a job executes it many times

4 Answers4

Linked