Home/ Questions/Q 6792115
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T17:55:45+00:00

I’ve got to write an app that performs a series of tasks: task to

  • 0

I’ve got to write an app that performs a series of tasks:

  1. task to be run once at 0200 hours every day.
  2. task to be run once at 0400 hours ever day
  3. task to be run at 15 minute intervals starting at 0003 hours
  4. task to be run at 15 minute intervals starting at 0005 hours

What are the pros and cons of using plain java.util.timer Vs. Quartz for this?

Are there any other alternatives I should be considering?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Quartz

    • Additional dependency
    • API currently (late 2011) changing: 1.x on its way out, but the only one supported by Spring and possibly others
    • Jobs can be stored persistently; multiple Schedulers can be clustered for load balancing and failover
    • The differentiation between Job and Trigger takes a bit getting used to – but it is possible to
    • More powerful repeated scheduling expressions (e.g. CronTrigger for cron expressions)

    Timer

    • Comes with JSE 1.3+ out of the box
    • For your functionality probably enough
    • Less flexible, but less complex as well

    I am personally using Quartz + persistent storage for a Web application where triggers can be created interactively and should survive restarts, using Spring’s scheduling abstraction. Both APIs IMHO lack an important concept: retrying failed tasks after a certain period of time. Adding this for myself was a pain for repeated tasks that should be retried as well.

    • 0