Uploaded image for project: 'Quartz Scheduler (Historical - Do Not File New Issues Here - See GitHub)'
  1. Quartz Scheduler (Historical - Do Not File New Issues Here - See GitHub)
  2. QTZ-181

Scheduler tries to handle misfires after resumeAll even though it's in standby mode



    • Type: Bug
    • Status: Closed
    • Priority: 2 Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.4
    • Fix Version/s: 2.1
    • Component/s: JDBC JobStores
    • Labels:
    • Terracotta Target:
      Quartz 2.1.0
    • Fixed In Revision:


      I'm writing a small command tool that initializes a Scheduler (I don't call start on it) that connects to a db that other 2 schedulers use and issues pauseAll and resumeAll commands. I'm hoping to be able to pause the execution of triggers in the whole system for some time and then resume them. As I want this to be a "universal tool", it doesn't have any job detail classes in it.

      When it runs in "pause mode", I can pause all the triggers easily and I see in the database that all the triggers get paused. The problem appears when it runs in "resume mode": when the call to scheduler.resumeAll() is issued, everything blocks for a while and then I get an exception about the scheduler being unable to update a trigger because of a ClassNotFoundException.

      If I understand correctly what is happening, even though I don't start the scheduler, when I call resumeAll, all the misfired triggers must be handled and some of them get to this instance of the scheduler (shouldn't it be in "standby"?), which has no job detail classes.

      I'm currently using 1.8.4, so I don't know if it affects the other versions.




            • Assignee:
              cdennis Chris Dennis
              shobo Octav C
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: