Uploaded image for project: 'JS - JobScheduler'
  1. JS - JobScheduler
  2. JS-1492

JobScheduler hangs if an order job has an end time in its current run time period and the task of the job needs more time

    XMLWordPrintable

    Details

    • Type: Fix
    • Status: Released (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.8.4, 1.9.7, 1.10.1, 1.11
    • Component/s: None
    • Labels:
      None

      Description

      Current Situation
      An order job has a run time with a begin/end interval and let_run="no" (default)

      <job order="yes">
          <script  language="shell">
              <![CDATA[
      @echo off
      ping -n 1 -w 180000 1.1.1.1 > nul
      exit 0
              ]]>
          </script>
      
          <run_time >
              <weekdays >
                  <day  day="1 2 3 4 5 6 7">
                      <period  begin="21:00" end="21:10"/>
                  </day>
              </weekdays>
          </run_time>
      </job>
      

      If this example job is started by an order at 21:08 then it needs longer (3 min) than the end time 21:10 is reached.

      • In this case the JobScheduler hangs. It means
        • ... no answer per TCP
        • ... no further log line.
      • It seems dead but e.g. a windows service is still running
      • This issue doesn't occur if let_run="yes".

      Desired Behavior

      Workaround
      Configure the period in the job's run time with let_run="yes".

      <period  begin="21:00" end="21:10" let_run="yes"/>
      

        Attachments

          Activity

            People

            • Assignee:
              jz Joacim Zschimmer
              Reporter:
              oh Oliver Haufe
              Approver:
              Oliver Haufe
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: