Quartz trigger state is not persisting on server start -

We need to stop the job before applying maintenance. We are using quartz 2.2.1 in the cluster. The database is Oracle

I have developed a screen with "pause" functionality I saw that "break" works properly until I start the server again.

Anyone can please provide the signal.

Thank you very much earlier.

Rgds - Roy

If you have overwritten then existing job = true (focus Given that the default value is wrong) every time the server starts, it loads the job / trigger from the configuration file and replaces the existing one (who have the same work / trigger name), hence triggers and their cases Also overwrite in your case.

You can try to overwrite the existing jobs = wrong schedulerfirstben. Although this may not be convenient for you, because if you ever change the job configuration in the server, then existing jobs with the old configuration will remain in the database.

  & lt; Bean class = "org. Springframework.scheduling.quartz.SchedulerFactoryBean" & gt; .... & lt; Property Name = "Overwrite Exchanges" value = "false" /> & Lt; Property Name = "Trigger" & gt; & Lt; List & gt; .... & lt; / List & gt; & Lt; / Property & gt; .... and lt; / Bean & gt;