Quartz Scheduler(2.2.1) - Usage of SimpleTrigger

标签：

SimpleTrigger should meet your scheduling needs if you need to have a job execute exactly once at a specific moment in time, or at a specific moment in time followed by repeats at a specific interval. For example, if you want the trigger to fire at exactly 11:23:54 AM on January 13, 2015, or if you want it to fire at that time, and then fire five more times, every ten seconds.

With this description, you may not find it surprising to find that the properties of a SimpleTrigger include: a start-time, and end-time, a repeat count, and a repeat interval. All of these properties are exactly what you‘d expect them to be, with only a couple special notes related to the end-time property.

The repeat count can be zero, a positive integer, or the constant value SimpleTrigger.REPEAT_INDEFINITELY. The repeat interval property must be zero, or a positive long value, and represents a number of milliseconds. Note that a repeat interval of zero will cause ‘repeat count‘ firings of the trigger to happen concurrently (or as close to concurrently as the scheduler can manage).

If you‘re not already familiar with Quartz‘s DateBuilder class, you may find it helpful for computing your trigger fire-times, depending on the startTime (or endTime) that you‘re trying to create.

The endTime property (if it is specified) overrides the repeat count property. This can be useful if you wish to create a trigger such as one that fires every 10 seconds until a given moment in time. Rather than having to compute the number of times it would repeat between the start-time and the end-time, you can simply specify the end-time and then use a repeat count of REPEAT_INDEFINITELY (you could even specify a repeat count of some huge number that is sure to be more than the number of times the trigger will actually fire before the end-time arrives).

Examples of Defining Triggers with Different Schedules

The following are various examples of defining triggers with simple schedules. Review them all, as they each show at least one new/different point.

Also, spend some time looking at all of the available methods in the language defined by TriggerBuilder and SimpleScheduleBuilder so that you can be familiar with options available to you that may not have been demonstrated in the examples shown here.

Build a trigger for a specific moment in time, with no repeats

SimpleTrigger trigger = (SimpleTrigger) JobBuilder.newTrigger()  
    .withIdentity("trigger1", "group1") 
    .startAt(myStartTime) // some Date  
    .forJob("job1", "group1") // identify job with name, group strings 
    .build();

Build a trigger for a specific moment in time, then repeating every ten seconds ten times:

trigger = JobBuilder.newTrigger() 
    .withIdentity("trigger3", "group1") 
    .startAt(myTimeToStartFiring)  // if a start time is not given (if this line were omitted), "now" is implied 
    .withSchedule(SimpleScheduleBuilder.simpleSchedule() 
        .withIntervalInSeconds(10) 
        .withRepeatCount(10)) // note that 10 repeats will give a total of 11 firings 
    .forJob(myJob) // identify job with handle to its JobDetail itself                    
    .build();

Build a trigger that will fire once, five minutes in the future

trigger = (SimpleTrigger) JobBuilder.newTrigger()  
    .withIdentity("trigger5", "group1") 
    .startAt(DateBuilder.futureDate(5, IntervalUnit.MINUTE)) // use DateBuilder to create a date in the future 
    .forJob(myJobKey) // identify job with its JobKey 
    .build();

Build a trigger that will fire now, then repeat every five minutes, until the hour 22:00

trigger = JobBuilder.newTrigger() 
    .withIdentity("trigger7", "group1") 
    .withSchedule(SimpleScheduleBuilder.simpleSchedule() 
        .withIntervalInMinutes(5) 
        .repeatForever()) 
    .endAt(dateOf(22, 0, 0)) 
    .build();

Build a trigger that will fire at the top of the next hour, then repeat every 2 hours, forever

trigger = JobBuilder.newTrigger() 
    .withIdentity("trigger8") // because group is not specified, "trigger8" will be in the default group 
    .startAt(DateBuilder.evenHourDate(null)) // get the next even-hour (minutes and seconds zero ("00:00")) 
    .withSchedule(SimpleScheduleBuilder.simpleSchedule() 
        .withIntervalInHours(2) 
        .repeatForever()) 
    // note that in this example, ‘forJob(..)‘ is not called  
    //  - which is valid if the trigger is passed to the scheduler along with the job   
    .build(); 
             
scheduler.scheduleJob(trigger, job);

SimpleTrigger Misfire Instructions

SimpleTrigger has several instructions that can be used to inform Quartz what it should do when a misfire occurs. (For information about misfires, see the About Triggers topic.) These instructions are defined as constants on SimpleTrigger itself (including Javadoc that describes their behavior). These constants include:

MISFIRE_INSTRUCTION_IGNORE_MISFIRE_POLICY 
MISFIRE_INSTRUCTION_FIRE_NOW 
MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_EXISTING_REPEAT_COUNT 
MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT 
MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT 
MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT

All triggers have the MISFIRE_INSTRUCTION_SMART_POLICY instruction available for use, and this instruction is the default for all trigger types.

If the ‘smart policy‘ instruction is used, SimpleTrigger dynamically chooses between its various misfile instructions, based on the configuration and state of the given SimpleTrigger instance. The Javadoc for the SimpleTrigger.updateAfterMisfire() method explains the details of this dynamic behavior.

When building SimpleTriggers, you specify the misfire instruction as part of the simple schedule (via SimpleSchedulerBuilder):

trigger = JobBuilder.newTrigger() 
    .withIdentity("trigger7", "group1") 
    .withSchedule(simpleSchedule() 
        .withIntervalInMinutes(5) 
        .repeatForever() 
        .withMisfireHandlingInstructionNextWithExistingCount()) 
    .build();

Quartz Scheduler(2.2.1) - Usage of SimpleTrigger

标签：

原文地址：http://www.cnblogs.com/huey/p/5106813.html