Orchestration instnaces are in ‘Ready to Run’ while recieve pipeline instances are being executed

I have created two biztalk applications: BizTalkApplication1 and BizTalkApplication2. each one has one Recieve location , one  orchestration and an Send port.

The BizTalkApplication1 orchestration is desinged with convoy pattern ( an Orchestration instances is intiliazed by a correlation set)

Both applications recieve locations processed by the RxHost host instance, Orchestration instances are processed by OrchHost host.

The bizTalkApplication1 receive pipeline contains flat file disassembler component.

I have placed a flat file (which contains more than 5000 records) in the BizTalkApplication1 recieve location.

The the BizTalkApplication1  Receive pipeline is started and dissassembling the flat file message. While the receive pipeline is being exected I have dropped a xml file  in BizTalkApplication2  reciegve location.

The  BizTalkApplication2 receive pipeline was completed, But When I checked the status of the BizTalkApplication2 in Administration Console, the Orchestration instances were in ‘Ready To Run’ state. I have tried restarting OrchHost host instance, still the orchestration instances are in ‘Ready To Run’.

I have noticed that the BizTalkApplication2  orchestration instances are started processing once the BizTalkApplication1  is completed.

.I have rested the above scenario for couple of time, still the BizTalkApplication2  orchestration are in ‘Ready to Run’ state while the BizTalkApplication1  receive location is being executed.

Can anybody tell me why the BizTalkapplication2 orch instnace are in ‘Ready To Run’ state while BizTalkApplication1 receive pipeline is being executed?

There are no common artificats between BizTalkapplication2  and BizTalkapplication1.

If BizTalkapplication1  and BizTalkapplication2  orchestration handler (hosts) are different, the BizTalkapplication2 orchestration is being processed successfully while BizTalkApplication1  receive location is being processed.

And If BizTalkapplication1  orchestration is impleted with convoy pattern, the ‘Ready to Run’ issue is not happening.