Uploaded image for project: 'Mule'
  1. Mule
  2. MULE-16759

WARN logged when fixed rate task overlap in a single thread Scheduler

    Details

    • Severity:
      S2
    • Bug Boosted:
      No
    • Defect Source:
      Production Defect
    • Story Points:
      0
    • Sprint:
      Mule 4 - Demeter 04/24
    • Severity Label:
      S2 (Regular)
    • Affects:
      nothing

      Description

      By default, when a Scheduler is busy and a task is submitted, a WARNing is logged to indicate that situation (as of MULE-14524).

      However, when dealing with repeatable jobs scheduled at fixed rate, it is not uncommon to have executions that take longer than the configured interval. The task itself will check if another instance is running and then cancel the new one, but in order to do that check it first has to be dispatched to a thread in the Scheduler. If the scheduler has only 1 thread (as is the case in the polling sources), the WARN indicating that the scheduler is busy is logged. In the case of overlapping repeatable jobs, the WARN must not be logged and the execution skipped silently.

      Apart form fixed rate, this can also happen when using cron expressions.

        Attachments

          Activity

            People

            • Assignee:
              rodrigo.merino Rodrigo Merino
              Reporter:
              rodrigo.merino Rodrigo Merino
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: