Jobs not starting with 2.0.12 on Grails 3.0.17

[zoladkow]

Hi,

On our project we decided to give version 2.0.12 a go (up from 2.0.8) and, from the logs of it, the jobs are not started.

application.yml:

quartz:
    autoStartup: true
    jdbcStore: false

One of the job triggers & config:

    static triggers = {
        simple name: 'ldapTrigger', startDelay: 30 * 1000, repeatInterval: 10 * 60 * 1000
    }
    String group = 'LdapGroup'
    String description = 'Synchronizes LDAP users into local cache'
    Boolean sessionRequired = Boolean.FALSE
    Boolean concurrent = Boolean.FALSE

Startup log related to Quartz:

2017-04-07 19:25:01.284 [main] INFO  [][] o.q.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor
2017-04-07 19:25:01.441 [main] INFO  [][] o.q.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2017-04-07 19:25:01.441 [main] INFO  [][] org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.2.3 created.
2017-04-07 19:25:01.460 [main] INFO  [][] org.quartz.simpl.RAMJobStore - RAMJobStore initialized.
2017-04-07 19:25:01.461 [main] INFO  [][] org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v2.2.3) 'quartzScheduler' 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.

2017-04-07 19:25:01.461 [main] INFO  [][] o.q.impl.StdSchedulerFactory - Quartz scheduler 'quartzScheduler' initialized from an externally provided properties instance.

2017-04-07 19:25:01.461 [main] INFO  [][] o.q.impl.StdSchedulerFactory - Quartz scheduler version: 2.2.3
2017-04-07 19:25:01.463 [main] INFO  [][] org.quartz.core.QuartzScheduler - JobFactory set to: grails.plugins.quartz.GrailsJobFactory@57554f95

Will also try with 2.0.11 and get back with result...

[davydotcom]

It will say not started in that log and it starts later

…

Sent from my iPhone

On Apr 7, 2017, at 1:17 PM, zoladkow ***@***.***> wrote: Hi, On our project we decided to give version 2.0.12 a go (up from 2.0.8) and, from the logs of it, the jobs are not started. application.yml: quartz: autoStartup: true jdbcStore: false One of the job triggers & config: static triggers = { simple name: 'ldapTrigger', startDelay: 30 * 1000, repeatInterval: 10 * 60 * 1000 } String group = 'LdapGroup' String description = 'Synchronizes LDAP users into local cache' Boolean sessionRequired = Boolean.FALSE Boolean concurrent = Boolean.FALSE Startup log related to Quartz: 2017-04-07 19:25:01.284 [main] INFO [][] o.q.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor 2017-04-07 19:25:01.441 [main] INFO [][] o.q.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2017-04-07 19:25:01.441 [main] INFO [][] org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.2.3 created. 2017-04-07 19:25:01.460 [main] INFO [][] org.quartz.simpl.RAMJobStore - RAMJobStore initialized. 2017-04-07 19:25:01.461 [main] INFO [][] org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v2.2.3) 'quartzScheduler' 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. 2017-04-07 19:25:01.461 [main] INFO [][] o.q.impl.StdSchedulerFactory - Quartz scheduler 'quartzScheduler' initialized from an externally provided properties instance. 2017-04-07 19:25:01.461 [main] INFO [][] o.q.impl.StdSchedulerFactory - Quartz scheduler version: 2.2.3 2017-04-07 19:25:01.463 [main] INFO [][] org.quartz.core.QuartzScheduler - JobFactory set to: ***@***.*** Will also try with 2.0.11 and get back with result... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[zoladkow]

Ok, my bad. I did not mention that this was the only log fragment related to this plugin. Even after a few minutes.
There are 4 jobs we have. None started. The one shown above should start with a delay of 30s.
Can't see what changed that could impact this, did I miss a new mandatory setting?

A breakpoint at QuartzGrailsPlugin.onStartup() was not hit if that helps.

[davydotcom]

I wonder if onStartup isn't triggered by Grails 3.0.x

…

Sent from my iPhone

On Apr 7, 2017, at 2:47 PM, zoladkow ***@***.***> wrote: Ok, my bad. I did not mention that this was the only log fragment related to this plugin. Even after a few minutes. There are 4 jobs we have. None started. The one shown above should start with a delay of 30s. Can't see what changed that could impact this, did I miss a new mandatory setting? A breakpoint at QuartzGrailsPlugin.onStartup() was not hit if that helps. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[zoladkow]

So the same happens for 2.0.10, 2.0.11

The thing is that in 2.0.9 there is no onStartup() at all, just doWithApplicationContext(). I was only looking through release changes and missed that (5d08900).

So basically 2.0.9 is the last version compatible with Grails 3.0.x right?

[davydotcom]

Seems so but it was starting too early... the best solution is to probably kick startup off via bootstrap... ill check with graeme

…

On Apr 8, 2017 5:27 AM, "zoladkow" ***@***.***> wrote: So the same happens for 2.0.10, 2.0.11 The thing is that in 2.0.9 there is no onStartup() at all, just doWithApplicationContext(). I was only looking through release changes and missed that (5d08900 <5d08900> ). So basically 2.0.9 is the last version compatible with Grails 3.0.x right? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#87 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABaEuDPitHCxvwqZnVUEUfwN-73yB0Mks5rt2EBgaJpZM4M3OXQ> .

[dcbenwu]

Jobs not start after a few days. quartz:2.0.12 with grails 3.2.11.
I config a job like "cron name: 'ScanJob', cronExpression: "0 30 0 * * ? *"
no exception comes out? How to track it?

[ppazos]

jobs are not starting in grails 3.3.10 with quartz 2.0.13

[j1m-renwick]

So the same happens for 2.0.10, 2.0.11

The thing is that in 2.0.9 there is no onStartup() at all, just doWithApplicationContext(). I was only looking through release changes and missed that (5d08900).

So basically 2.0.9 is the last version compatible with Grails 3.0.x right?

@zoladkow @davydotcom I know this is a very old thread but do you remember anything about the outcome of this? Our application on Grails 3.2.13 is having start-up issues using any Quartz plugin version after 2.0.9 - the bootstrap class is not being run on application startup, and the Quartz plugin version seems to be the reason why...

[zoladkow]

@zoladkow @davydotcom I know this is a very old thread but do you remember anything about the outcome of this? Our application on Grails 3.2.13 is having start-up issues using any Quartz plugin version after 2.0.9 - the bootstrap class is not being run on application startup, and the Quartz plugin version seems to be the reason why...

@j1m-renwick I believe we moved to Grails 3.3.11 (which had a bunch of other quirks on it's own) and stick to Quartz plugin 2.0.9 to this day since newer versions didn't bring anything of value anyways... unless I'm wrong.

Wow, 4 years already, time sure flies...