Home/ Questions/Q 7901939
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T09:21:50+00:00

I need a mechanism for implementing asynchronous job scheduling in Java and was looking

  • 0

I need a mechanism for implementing asynchronous job scheduling in Java and was looking at the Quartz Scheduler, but it seems that it does not offer the necessary functionality.

More specifically, my application, which runs across different nodes, has a web-based UI, via which users schedule several different jobs. When a job is completed (sometime in the future), it should report back to the UI, so that the user is informed of its status. Until then, the user should have the option of editing or cancelling a scheduled job.

An implementation approach would be to have a Scheduler thread running constantly in the background in one of the nodes and collecting JobDetail definitions for job execution.

In any case, there are two the questions (applicable for either a single-node or multi-node scenario):

  1. Does Quartz allow a modification or a cancellation of an already scheduled job?
  2. How can a “callback” mechanism be implemented so that a job execution result is reported back to the UI?

Any code examples, or pointers, are greatly appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. Does Quartz allow a modification or a cancellation of an already scheduled job?

    You can “unschedule” a job:

    scheduler.unscheduleJob(triggerKey("trigger1", "group1"));

    Or delete a job:

    scheduler.deleteJob(jobKey("job1", "group1"));

    As described in the docs:

    http://quartz-scheduler.org/documentation/quartz-2.x/cookbook/UnscheduleJob

    Note, the main difference between the two is unscheduleing a job removes the given trigger, while deleting the job removes all triggers to the given job.

    1. How can a “callback” mechanism be implemented so that a job execution result is reported back to the UI?

    Typically, in the web world, you will poll the web server for changes. Depending upon your web framework, there may be a component available (Push, Pull, Poll?) that makes this easy. Also, what you will need to do is store some state about your job on the server. Once the job finishes you may update a value in the database or possibly in memory. This, in turn, would be picked up by the polling and displayed to the user.

    • 0