In the previous chapters, we didn't spend any time discussing where the job and trigger information for the Scheduler was stored. You might have realized, however, that when you stopped the Scheduler, the knowledge of which jobs had run and which ones had not was lost. In fact, all the information about the running jobs was destroyed.
When the application was restarted, the trigger and job information was added back, and everything was fine again. Suppose, however, that a job was scheduled for execution at 5 PM and the Scheduler was stopped five minutes before that time, at 4:55 PM. What would happen if you restarted the Scheduler at 5:05 PM? Would the Scheduler remember that it was supposed to fire the job at 5 PM? The answer is that it depends on which type of JobStore you're using and how you have it configured.
Scheduling in the Enterprise
Getting Started with Quartz
Hello, Quartz
Scheduling Jobs
Cron Triggers and More
JobStores and Persistence
Implementing Quartz Listeners
Using Quartz Plug-Ins
Using Quartz Remotely
Using Quartz with J2EE
Clustering Quartz
Quartz Cookbook
Quartz and Web Applications
Using Quartz with Workflow
Appendix A. Quartz Configuration Reference