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-201

Semantics of Scheduler.pauseTriggers(groupMatcher) and getPausedTriggerGroups() are broken for not-yet-existing groups.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: 2 Major
    • Resolution: Fixed
    • Affects Version/s: 2.0, 2.0.1, 2.0.2
    • Fix Version/s: 2.1
    • Component/s: Core
    • Labels:
      None
    • Terracotta Target:
      Quartz 2.1.0
    • Fixed In Revision:
      1644,29464

      Description

      There is a logic bug in the Terracotta JobStore (DefaultClusteredJobStore class, to be precise).

      It also appears that the same bug likely exists in RAMJobStore.

      Furthermore I can see that there is a semantic problem with the JobStore.pauseTriggers method that leads to this problem, and the bug may likely also exist in JDBCJobStore as well.

      The problem is that the method now (since 2.0) takes a GroupMatcher, which isn't necessarily an exact group name (e.g. could be a start with or contains etc. rather than an equals). That means the current set of groups must be iterated over to see which ones match. If there are no triggers in the group, then it isn't there to be iterated over and considered a match!

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jhouse James House
                Reporter:
                jhouse James House
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: