Job Stream marked as completed

Current Situation

When a job stream is running then after each task a check is performed if the job stream is completed. Automatic detection is in place, in addition an explicit detection is available by specifying the last job in the job stream with the job stream starter.

The rule for automatic detection is

"running is true if there is at least one local not global event in the conditions not yet consumed that is created by a local Out-Condition"

In case that an In-Condition does not have a local event, this job is not considered for automatic detection. E.g. the In-Condition myStream.myEvent does not contain an event assigned to the running instance.

When for this case the job stream starter specifies the last job then this setting in the job stream starter is not considered. Therefore the job stream might be marked as completed too early.

Desired Behavior

When the last job is specified with the job stream starter definition then the job stream should be considered being completed when this job has been executed in the current job stream instance. No automatic detection should take place.

Workaround

When referring to an event using the jobstream.event syntax then add an event to the condition that is assigned the job stream instance e.g. myStream.myEvent and dummy. Then create the dummy event somewhere in the job stream.

Patch

A patch is available

• download from here
• Unzip the file to .jar
• store the jar file to $SCHEDULER_HOME/lib/patches
• if you already have installed patch {{patch-20210720 }} from "JS-1934.1.13.9.jar" then remove the old patch
• restart JobScheduler Master