Quartz autoStartup too early about grails-quartz HOT 5 CLOSED

Not to diminish the issue, but you could use startDelay as a workaround, correct?

from grails-quartz.

Not in JDBC clustered mode it assumed the delay has already been assessed

Sent from my iPhone

On Nov 1, 2016, at 5:28 PM, David Klebanoff [email protected] wrote:

Not to diminish the issue, but you could use startDelay as a workaround, correct?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

from grails-quartz.

I can verify this happening to us as well but I don't have a good fix yet.

from grails-quartz.

This fix with using onStartup requires at least grails 3.1.6 because it depends on this other fix: grails/grails-core#9883

from grails-quartz.

There is already a startupDelay implemented in SchedulerFactoryBean. One can configure it like this:

class Application extends GrailsAutoConfiguration {
  ...
  @Override
  Closure doWithSpring() {
    return { ->
      final quartzSchedulerDef = getBeanDefinition('quartzScheduler') as GenericBeanDefinition
      quartzSchedulerDef.propertyValues.addPropertyValue('startupDelay', TimeUnit.MINUTES.toSeconds(7))
    }
  }

has anyone tried that? So far I didn't find a problem with doing it this way.

from grails-quartz.