Grails 3(12) and quartz:2.0.5 not compiling or starting app

[netadmin2015]

Java 1.8
Grails 3.0.12

removed all cache files from anywhere I can think of

New project: grails create-app junk1
add compile 'org.grails.plugins:quartz:2.0.5' to build.gradle

grails
create-job Testme88

Edit Testme88Job and put:

1 package testme66
2
3 class Testme88Job {
4 static triggers = {
5 simple name: 'mySimpleTrigger', startDelay:5000, repeatCount: 1
6 }
7
8 def execute() {
9 log.debug("Domain name job processing");
10
11 }
12 }

All seems good.

Now

run-app

Lots of errors, This is the start of them.

Grails 3 / quartz 2.05 / java 1.8 / groovy 2.4.5

I am at a loss why I cannot get jobs to work.

Honestly grails 2.4.5 I do not have any issues and may not even upgrade to grails 3 as it seems to be a completely different animal.

Any ideas ?

From scratch out of the box does not seem to work at all.

HealthIndicatorAutoConfiguration.DiskSpaceHealthIndicatorConfiguration
- matched (OnPropertyCondition)
Exception in thread "main" org.springframework.context.ApplicationContextException: Failed to start bean 'quartzScheduler'; nested exception is org.springframework.scheduling.SchedulingException: Could not start Quartz Scheduler; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Table "QRTZ_LOCKS" not found; SQL statement:
SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'quartzScheduler' AND LOCK_NAME = ? FOR UPDATE [42102-176] [See nested exception: org.h2.jdbc.JdbcSQLException: Table "QRTZ_LOCKS" not found; SQL statement:
SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'quartzScheduler' AND LOCK_NAME = ? FOR UPDATE [42102-176]]]
at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:176)
at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:346)
at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:149)
at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:112)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:772)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.finishRefresh(EmbeddedWebApplicationContext.java:139)

[rvanderwerf]

You have to manually create the quartz tables... the plugin does not do
that for you. Download the quartz package from quartzscheduler.org and
create the tables for your DB under the doc directory. Or set
quartz.jdbcStore = false, for the RAMStore (no database).

On Fri, Jan 22, 2016 at 6:45 PM, netadmin2015 notifications@github.com
wrote:

Java 18
Grails 3012

removed all cache files from anywhere I can think of

New project: grails create-app junk1
add compile 'orggrailsplugins:quartz:205' to buildgradle

grails
create-job Testme88

Edit Testme88Job and put:

1 package testme66
2
3 class Testme88Job {
4 static triggers = {
5 simple name: 'mySimpleTrigger', startDelay:5000, repeatCount: 1
6 }
7
8 def execute() {
9 logdebug("Domain name job processing");
10
11 }
12 }

All seems good

Now

run-app

Lots of errors, This is the start of them

Grails 3 / quartz 205 / java 18 / groovy 245

I am at a loss why I cannot get jobs to work

Honestly grails 245 I do not have any issues and may not even upgrade to
grails 3 as it seems to be a completely different animal

Any ideas ?

From scratch out of the box does not seem to work at all

HealthIndicatorAutoConfigurationDiskSpaceHealthIndicatorConfiguration

• matched (OnPropertyCondition)
  Exception in thread "main"
  orgspringframeworkcontextApplicationContextException: Failed to start bean
  'quartzScheduler'; nested exception is
  orgspringframeworkschedulingSchedulingException: Could not start Quartz
  Scheduler; nested exception is orgquartzSchedulerConfigException: Failure
  occured during job recovery [See nested exception:
  orgquartzimpljdbcjobstoreLockException: Failure obtaining db row lock:
  Table "QRTZ_LOCKS" not found; SQL statement:
  SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'quartzScheduler' AND
  LOCK_NAME = ? FOR UPDATE [42102-176] [See nested exception:
  orgh2jdbcJdbcSQLException: Table "QRTZ_LOCKS" not found; SQL statement:
  SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'quartzScheduler' AND
  LOCK_NAME = ? FOR UPDATE [42102-176]]]
  at
  orgspringframeworkcontextsupportDefaultLifecycleProcessordoStart(DefaultLifecycleProcessorjava:176)
  at
  orgspringframeworkcontextsupportDefaultLifecycleProcessoraccess$200(DefaultLifecycleProcessorjava:51)
  at
  orgspringframeworkcontextsupportDefaultLifecycleProcessor$LifecycleGroupstart(DefaultLifecycleProcessorjava:346)
  at
  orgspringframeworkcontextsupportDefaultLifecycleProcessorstartBeans(DefaultLifecycleProcessorjava:149)
  at
  orgspringframeworkcontextsupportDefaultLifecycleProcessoronRefresh(DefaultLifecycleProcessorjava:112)
  at
  orgspringframeworkcontextsupportAbstractApplicationContextfinishRefresh(AbstractApplicationContextjava:772)
  at
  orgspringframeworkbootcontextembeddedEmbeddedWebApplicationContextfinishRefresh(EmbeddedWebApplicationContextjava:139)

—
Reply to this email directly or view it on GitHub
#53.

[AlexKovynev]

RAMStore not working from 2.0.2. Pull request awaiting!:)

[netadmin2015]

Using grails, the development mode has a database that is removed after you stop-app. I guess I could put those create tables in the Bootstrap and have them run each time. I assume version 2 had all this by default and it was removed for this version of the plugin.

I am use to (spoiled) by the Grails 2 version of everything. Grails 3 in almost every situation requires handholding. I decided to just download the jar files and not use the plugin. Found out that grails 3 does not even have a lib directory anymore.

Anyhow thanks again.

[AlexKovynev]

Use 2.0.1 plugin version! Or wait before rvanderwerf apply my pull at last.
#51

[rvanderwerf]

this was fixed with #50 as far as the referred pull request and released today