New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grails version >= 3.3.0 ,not support disable concurrent of quartz plugin #91

puwanatfx opened this Issue Jul 21, 2017 · 3 comments


None yet
6 participants
Copy link

puwanatfx commented Jul 21, 2017


I'm testing grails 3.3.0.M1 and 3.3.0RC1
and found it's not support disble concurrent job of quartz

compile 'org.grails.plugins:quartz:2.0.12'

disable concurrent job didn't work

def concurrent = false
I test with code

class TestJob {

def concurrent = false

static triggers = {
    cron name: 'myTrigger', cronExpression: "0/5 * * * * ?"

def execute() {
    // execute job
    log.error('Start:' + new Date())
    log.error('End:' + new Date())

When I run with grails 3.2.9 , it run fine , but if I run with newer version ,
I can not disable concurrent job

@kefirfromperm kefirfromperm added the bug label Jul 21, 2017


This comment has been minimized.

Copy link

sdelamo commented Jul 21, 2017

In case you need a fix fast, I am using Schwartz Plugin with 3.3.0.RC1 and the avoid concurrent annotation works.


This comment has been minimized.

Copy link

mamunsrdr commented Aug 30, 2017

Until 2.0.13 is released I'm using the 2.0.13.BUILD-20170829.124724-2.jar version as a local gradle jar dependency (to avoid unstable build I prefer tested local jar) downloaded from grails repo. Notice: this build requires change: job class property declaration to static. For example: static concurrent = false. My build.gradle looks like:

compile "org.quartz-scheduler:quartz:2.3.0"
//compile "org.grails.plugins:quartz:2.0.13.BUILD-SNAPSHOT"
compile files('libs/quartz-2.0.13.BUILD-SNAPSHOT.jar')

Tested with Grails 3.3.0.

@puneetbehl puneetbehl added this to the 2.0.13 milestone Jan 19, 2018

@puneetbehl puneetbehl closed this Jan 19, 2018


This comment has been minimized.

Copy link

erichelgeson commented Mar 12, 2018

What is the root requirement for changing this? I see the docs/commit were updated but not sure why the change was required. Deployed w/o changing this weekend and our jobs just didn't fire so it went unnoticed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment