Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
A job should start every day at 10:00. And additionally the day after tomorrow at 12:00 then the calculated next start time is the day after tomorrow 12:00
The run time is defined as
<run_time> <period single_start="10:00"/> <monthdays> <day day="15"> <period single_start="12:00"/> </day> </monthdays> </run_time>
- The behaviour is document here http://www.zschimmer.com/sos/scheduler/xml/run_time.html
- The period without a frequency is a period for all days
- If there is a frequency the period is a default for all frequencies.
- If the given frequencies are defining e.g. a period with a single start, the default period will be overwritten.
JOE generates the run time for the frequency every day as a default period that will be overwritten when another frequency defines a period.
Desired Behaviour
As the actual behaviour is very confusing when defining frequencies JOE should generate the every day frequency not with the default period but with the day frequency like this
<run_time> <weekdays> <day day="1 2 3 4 5 6 7"> <period single_start="10:00"/> </day> </weekdays> </run_time>
When defining an every day frequency an additional frequency the every day frequency should be active. A job should start every day at 10:00. And additionally the day after tomorrow at 12:00 then the calculated next start time should be today 10:00. This will be achieved by generating this run time configuration.
<run_time> <weekdays> <day day="1 2 3 4 5 6 7"> <period single_start="10:00"/> </day> </weekdays> <monthdays> <day day="15"> <period single_start="12:00"/> </day> </monthdays> </run_time>
Attachments
Issue Links
- is related to
-
JS-120 <run_time once="yes"/> is not considered on startup of the Job Scheduler
- Dismissed