BPEL: Resolving ConflictingReceive Issue while using the same PL in the branches of Flow or FlowN

Issue: 

Developers often encountered conflictingReceive fault while using the same partnerlink in different branches of Flow or FlowN.



Details following:



"{http://schemas.xmlsoap.org/ws/2003/03/business-process/}conflictingReceive"

    has been

     thrown."{http://schemas.xmlsoap.org/ws/2003/03/business-process/}conflictingReceive"

    has been thrown.

     



     

     *summary*">

     
Conflicting receive. A similar receive activity is being

     declared in the same process. Another receive activity or

     equivalent (currently, onMessage branch in a pick activity) has

     already been enabled with the partnerLink "Dummy", operation name

     "processResponse" and correlation set "" (or conversation ID).

     Appendix A - Standard Faults in the BPEL 1.1 specification

     specifies a fault should be thrown under these conditions.

     Redeploy the process after removing the conflicting receive

    activities. 

   

     



Solution:

Instead of defining the partnerlink as a global partner link, declare it within a scope of each parallel branch.