Coffee time. Coffee time. Coffee time. Alex smiled. For the first time, time felt controllable . Emboldened, Alex tried to fix the 1:30 AM report. A junior mistake was made: Copy-pasting a cron expression from Stack Overflow.
Alex deployed it. The next Sunday at (not AM), the test database was slammed with 10,000 queries.
0 30 13 ? * SUN
That was the last straw. Alex went back to the ebook draft (the one you are now reading) and found .
public class RetryListener implements JobListener { public void jobWasExecuted(JobExecutionContext context, JobExecutionException exception) { if (exception != null && context.getRefireCount() < 3) { context.setRefireCount(context.getRefireCount() + 1); // Re-run the job immediately } } } Alex added three lines to the scheduler config. The next time the gateway failed, Quartz waited 10 seconds, tried again, and succeeded. Quartz Job Scheduler Ebook
And that, Alex thought, was the difference between putting out fires and building a system that breathes on its own.
She handed Alex a sticky note with the golden rule: The correct fix for 1:30 AM every weekday: 0 30 1 ? * MON-FRI Coffee time
Standard Timer and ScheduledExecutorService in Java couldn't handle that complexity. They were like alarm clocks that only rang once. Alex needed a Swiss Army knife for time.