According to Quartz CronTrigger source code the trigger retains the date of the next time it should fire.
According to Quartz CronTrigger source code, the trigger retains the date of the next time it should fire. I suppose that if you start the server at 6:15:00, Quartz retains 7:00:00 as the next firing time. Changing the server time to 5:55:45 doesn't update the next firing time, and 7:00:00 is retained as next firing time.So the event won't fire at 6:00:00, but instead at 7:00:00.
So, time isn't retained directly, but firing time is retained, and it appears it isn't updated if you change your system clock.
If you use JDBC job store, quartz checks database in one-minute intervals looking for jobs to run for now, using the current system time. When you move forward the system time, quartz will fire appropriate jobs on next check (that means, within minute).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.