max_orders=1 configuration has no effect when multiple simultaneous Orders are submitted to a job chain with split and sync nodes

Current Situation

• This scenario assumes a split and sync job chain is configured with max_orders=1.
• After split node there are three jobs configured to be run in parallel e.g. Job01_P1, Job02_P2 and Job03_P3.
• When multiple orders are submitted to the job chain, only one order will enter the job chain. Rest of the orders will wait at the first node of the job chain due to configuration max_orders=1.
• When the first order reaches at split node, split node creates three child orders for the jobs set to run in parallel.
• As soon as split node creates three child orders, all the orders waiting at the first node enter the job chain.
• This behavior shows that the max_orders=1 has no effect on split and sync job chains.
• Above mentioned behavior can also be observed in a job chain configured with file order source.

How to Reporduce

• See the attached test case FileOrderSplitSyncMaxOrder1.zip
• Split Sync job chain visualization
• 

Desired Behavior

• When a split and sync job chain is configured with max_orders=1 only one main order should be allowed to enter the job chain.
• One main order can create n child orders to executed parallel jobs.

Workaround

• How to prevent concurrent access to resources by parallel execution of orders in job chains

Sourceforge Discussion

• Split/Sync breaks SCHEDULER_RETURN_VALUES and max_orders