任务调度框架Quartz快速入门

最新推荐文章于 2024-09-01 16:17:46 发布

2401_84010457

最新推荐文章于 2024-09-01 16:17:46 发布

阅读量1k

点赞数 8

分类专栏：程序员文章标签： microsoft 数据库 windows

本文链接：https://blog.csdn.net/2401_84010457/article/details/137206757

版权

程序员专栏收录该内容

237 篇文章 0 订阅

订阅专栏

超重要API

==========

Scheduler 和调度程序交互的主要API生命周期从SchedulerFactoru创建它开始，到调用shutdown方法结束。一旦Scheduler创建，任何关于scheduling相关的事，他都为所欲为：添加、删除、列出所有的Jobs和triggers、暂停触发器等。在start方法之前，不会做任何事情。
Job 你希望被调度器调度的任务组件接口。当Job的触发器触发时，调度程序的工作线程将调用execute方法。该方法接收一个JobExecutionContext对象，为Job实例提供了丰富的运行时环境信息，比如：scheduler、trigger、jobDataMap、job、calendar、各种time等。
JobDetail 用于定义任务。JobDetail对象由Quartz客户端在将job加入Scheduler提供，也就是你的程序。它包含了不同为job设置的属性，还有可以用来为job储存状态信息的JobDataMap。注意它和Job的区别，它实际上是Job实例的属性。【Job定义如何执行，JobDetail定义有何属性】
Trigger 触发任务执行。触发器可能具有与之关联的JobDataMap，以便于将特定于触发器触发的参数传递给Job。Quartz提供了几种不同的触发器，SimpleTrigger和CronTrigger比较常用。如果你需要一次性执行作业或需要在给定的时间触发一个作业并重复执行N次且有两次执行间有延时delay，SimpleTrigger较为方便。如果你希望基于类似日期表触发执行任务，CronTrgger推荐使用。
JobBuilder 用于构建JobDetail的。
TriggerBuilder 用于构建Trigger的。

Quartz提供了各种各样的Builder类，定义了Domain Specific Language，且都提供了静态的创建方法，我们可以使用import static简化书写。

重要概念

========

Identity当作业和触发器在Quartz调度程序中注册时，会获得标识键。JobKey和TriggerKey允许被置入group中，易于组织管理。唯一的，是name和group的组合标识。
JobDataMap是Map的实现，具有key-value相关操作，存储可序列化数据对象，供Job实例在执行时使用。可以使用usingJobData(key,value)在构建Jobdetail的时候传入数据，使用jobDetail.getJobDataMap()获取map。

Quartz设计理念：为什么设计Job和Trigger？

================================

While developing Quartz, we decided that it made sense to create a separation between the schedule and the work to be performed on that schedule. This has (in our opinion) many benefits. For example, Jobs can be created and stored in the job scheduler independent of a trigger, and many triggers can be associated with the same job. Another benefit of this loose-coupling is the ability to configure jobs that remain in the scheduler after their associated triggers have expired, so that that it can be rescheduled later, without having to re-define it. It also allows you to modify or replace a trigger without having to re-define its associated job.

隔离schedule和schedule上执行的Job，优点是可见的：

可以独立于触发器创建作业并将其存储在作业调度程序中，并且许多触发器可以与同一作业相关联。这样的松耦合好处是什么？

如果触发器过期，作业还可以保留在程序中，以便重新调度，而不必重新定义。
如果你希望修改替换某个触发器，你不必重新定义其关联的作业。

最简单的Quartz使用案例

==================

导入依赖

org.quartz-scheduler

quartz

2.3.2

简单案例如下

public class QuartzTest {

// 你需要在start和shutdown之间执行你的任务。

public static void main(String[] args) {

try {

// 从工厂中获取Scheduler示例

Scheduler scheduler = StdSchedulerFactory.getDefaultScheduler();

// 开始

scheduler.start();

// 定义Job，并将其绑定到HelloJob类中

JobDetail job = JobBuilder.newJob(HelloJob.class)

.withIdentity(“job1”, “group1”) // name 和 group

.usingJobData(“username”, “天乔巴夏”) // 置入JobDataMap

.usingJobData(“age”, “20”)

.withDescription(“desc-demo”)

.build();

// 触发Job执行，每40s执行一次

Trigger trigger = TriggerBuilder.newTrigger()

.withIdentity(“trigger1”, “group1”)

.startNow() // 立即开始

.withSchedule(SimpleScheduleBuilder.simpleSchedule()

.withIntervalInSeconds(40)

.repeatForever())

.build();

// 告诉 quartz 使用trigger来调度job

scheduler.scheduleJob(job, trigger);

// 关闭，线程终止

scheduler.shutdown();

} catch (SchedulerException se) {

se.printStackTrace();

}

@Slf4j

@NoArgsConstructor

public class HelloJob implements Job {

@Override

public void execute(JobExecutionContext context) throws JobExecutionException {

// 从context中获取属性

JobDetail jobDetail = context.getJobDetail();

JobDataMap jobDataMap = jobDetail.getJobDataMap();

JobKey key = jobDetail.getKey();

Class<? extends Job> jobClass = jobDetail.getJobClass();

String description = jobDetail.getDescription();

String username = jobDataMap.getString(“username”);

int age = jobDataMap.getIntValue(“age”);

log.info(“\nJobKey : {},\n JobClass : {},\n JobDesc : {},\n username : {},\n age : {}”,

key, jobClass.getName(), description, username, age);

}

启动测试，打印日志如下：

01:23:12.406 [main] INFO org.quartz.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor

01:23:12.414 [main] INFO org.quartz.simpl.SimpleThreadPool - Job execution threads will use class loader of thread: main

01:23:12.430 [main] INFO org.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

01:23:12.430 [main] INFO org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.3.2 created.

01:23:12.432 [main] INFO org.quartz.simpl.RAMJobStore - RAMJobStore initialized.

01:23:12.433 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v2.3.2) ‘DefaultQuartzScheduler’ with instanceId ‘NON_CLUSTERED’

Scheduler class: ‘org.quartz.core.QuartzScheduler’ - running locally.

NOT STARTED.

Currently in standby mode.

Number of jobs executed: 0

Using thread pool ‘org.quartz.simpl.SimpleThreadPool’ - with 10 threads.

Using job-store ‘org.quartz.simpl.RAMJobStore’ - which does not support persistence. and is not clustered.

01:23:12.433 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler ‘DefaultQuartzScheduler’ initialized from default resource file in Quartz package: ‘quartz.properties’

01:23:12.433 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler version: 2.3.2

01:23:12.434 [main] INFO org.quartz.core.QuartzScheduler - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

01:23:12.434 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG org.quartz.core.QuartzSchedulerThread - batch acquisition of 0 triggers

01:23:12.443 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG org.quartz.core.QuartzSchedulerThread - batch acquisition of 1 triggers

01:23:12.445 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG org.quartz.simpl.PropertySettingJobFactory - Producing instance of Job ‘group1.job1’, class=com.hyhwky.HelloJob

01:23:12.451 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG org.quartz.core.QuartzSchedulerThread - batch acquisition of 0 triggers

01:23:12.452 [DefaultQuartzScheduler_Worker-1] DEBUG org.quartz.core.JobRunShell - Calling execute on job group1.job1

01:23:12.452 [DefaultQuartzScheduler_Worker-1] INFO com.hyhwky.HelloJob -

JobKey : group1.job1,

JobClass : com.hyhwky.HelloJob,

JobDesc : desc-demo,

username : 天乔巴夏,

age : 20

我们可以看到quartz已经被初始化了，初始化配置如下，在org\quartz-scheduler\quartz\2.3.2\quartz-2.3.2.jar!\org\quartz\quartz.properties