Latest documentation and snapshots are available.
| Branch | Grails Version |
|---|---|
| 1.x | 2 |
| 2.0.x | 3-5 |
| 3.0.x | 6 |
To start using Quartz plugin just simply add
implementation 'org.grails.plugins:quartz:{version}' in your build.gradle.
Note
2.0.13 for Grails 3.3.*
Properties changed to static from def.
For example: def concurrent will be now static concurrent.
To create a new job run the grails create-job command and enter the name of the job. Grails will create a new job and place it in the grails-app/jobs directory:
package com.mycompany.myapp
class MyJob {
static triggers = {
simple repeatInterval: 1000
}
void execute() {
print "Job run!"
}
}The above example will call the execute() method every second.
Currently, plugin supports three types of triggers:
- simple trigger — executes once per defined interval (ex. "every 10 seconds");
- cron trigger — executes job with cron expression (ex. "at 8:00 am every Monday through Friday");
- custom trigger — your implementation of Trigger interface.
Multiple triggers per job are allowed.
class MyJob {
static triggers = {
simple name: 'simpleTrigger', startDelay: 10000, repeatInterval: 30000, repeatCount: 10
cron name: 'cronTrigger', startDelay: 10000, cronExpression: '0/6 * 15 * * ?'
custom name: 'customTrigger', triggerClass: MyTriggerClass, myParam: myValue, myAnotherParam: myAnotherValue
}
void execute() {
println "Job run!"
}
}With this configuration, job will be executed 11 times with 30 seconds interval with first run in 10 seconds after scheduler startup (simple trigger), also it'll be executed each 6 second during 15th hour (15:00:00, 15:00:06, 15:00:12, ... — this configured by cron trigger) and also it'll be executed each time your custom trigger will fire.
Three kinds of triggers are supported with the following parameters. The name field must be unique:
simple:name— the name that identifies the trigger;startDelay— delay (in milliseconds) between scheduler startup and first job's execution;repeatInterval— timeout (in milliseconds) between consecutive job's executions;repeatCount— trigger will fire job execution(1 + repeatCount)times and stop after that (specify0here to have one-shot job or-1to repeat job executions indefinitely);
cron:name— the name that identifies the trigger;startDelay— delay (in milliseconds) between scheduler startup and first job's execution;cronExpression— cron expression
custom:triggerClass— your class which implements CalendarIntervalTriggerImpl impl;- any params needed by your trigger.
You can add the following properties to control persistence or not persistence:
quartz.pluginEnabled- defaults totrue, can disable plugin for test cases etcquartz.jdbcStore-trueto enable database store,falseto use RamStore (default:true)quartz.autoStartup- delays jobs until after bootstrap startup phase (default:false)quartz.jdbcStoreDataSource- jdbc data source alternate namequartz.waitForJobsToCompleteOnShutdown- wait for jobs to complete on shutdown (default:true)quartz.exposeSchedulerInRepository- expose Schedule in repositoryquartz.scheduler.instanceName- name of the scheduler to avoid conflicts between appsquartz.purgeQuartzTablesOnStartup- when jdbcStore set totrueand this istrue, clears out all quartz tables on startup
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent