• Quartz Java resuming a job excecutes it many times--转


    原文地址:http://stackoverflow.com/questions/1933676/quartz-java-resuming-a-job-excecutes-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 instruciton upon creation to this :

    trigger.setMisfireInstruction(CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING);
    

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

    answer:

    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;
        }
    }
  • 相关阅读:
    uva 10370
    uva 10107
    uva 10038
    uva 488
    伪代码格式
    公众号的秘密,知道一个biz就够了
    ToolTip 概述
    swt
    Java GUI图形界面开发工具
    Java多线程-两个小球
  • 原文地址:https://www.cnblogs.com/davidwang456/p/5482858.html
Copyright © 2020-2023  润新知