chamithkodikara / quartz-demo Goto Github PK

ERROR: This scheduler instance (86825868-6f63-4589-ba41-291d3aff6fc8) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior.
I google this,find nothing,hope you can help me

running "mvn test". should not come to a halt because the system upon which this is run is not configured in some predefined way.

I would suggest either

a). Test are setup to run with H2. an in-jvm-process database which is SQL compliant.

or

b) if you must use a "real" database like Postgres or mysql that you use some one of the "test container" database setups. In this way all that's needed is docker. All the other details are "fixed" within your test setup.

Why not create the Job by set isDurable: true here, and without saving it by schedulerRepository?

Hi, I an trying to update the cron expression to "0 0/1 0 ? * *" from a custom controller using the "updateScheduleJob" method. The details get updated in the DB table "scheduler_job_info" but the trigger stops firing after the update and the trigger state becomes "WAITING". How can I update the cron schedule in DB without restarting the application ?
Thanks in advance.

As it is defined in the application.properties it should use
spring.quartz.properties.org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX

but when running the application it actually uses
org.quartz.impl.jdbcjobstore.JobStoreCMT
which does not manage the transactions, so the example fails in a clustered environment.