Khanderao on Emerging And Integration Technologies

Tuesday, June 23, 2009

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


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

Details following:

has been
has been thrown.

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

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

Add to Technorati Favorites

Save This Page on


Post a Comment

<< Home