Only in conditions of the running job stream should be considered

Current Situation
The in condition of all job streams are considered when examining a running job stream instance. This will perform a lot of irrelevant checks for in conditions and therefore will downgrade the performance especially when many job streams with many jobs are configured.

Another effect ist hat jobs will be started when they have expression with a jobstream assignment like aJobStream.myEvent each time any job stream is running.

How To Reproduce

• Create two Job Streams in the same folder (e.g. jobstream1 and jobstream2) with their Starters (e.g. starter1 and starter2)
• Add jobs to them (e.g. job1 --> job2 on jobstream1) and (e.g. job3 on jobstream2)
• Add an OutCondition on job2 (e.g. create event "event2")
• Add an InCondition on job3 (e.g. "event2")
• Start the Starter of jobstream1 (e.g. starter1)
• You will find that job3 is also executing even if the starter2 is not started yet

Desired Behavior

• When examining a running job stream only in conditions that belongs to this job stream should be considered.

Patch

A patch is available

•  1.13.5 here.
•  1.13.6 here.

Please download the .jar file and copy the file to $scheduler_home/patches/lib
The patch also contains the patch for JS-1897. If you have installed this (patch_sos-jobstreams_JS-1897.1.13.6) , please remove this. Then restart JobScheduler.