conflictingReceive Behavior Different for Pick/onMessage Versus Receive

(Doc ID 755201.1)

Last updated on NOVEMBER 19, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.3
This problem can occur on any platform.

Symptoms

On 10.1.3.3.1 in Production:
After initiating a second test instance for a BPEL process with a Receive activity with the same
correlation set as the first test instance, when invoking the partnerLink with the same portType
and operation, it rightly throws the following fault:
.
<?xml version="1.0" encoding="UTF-8" ?>
- <part>
- <conflictingReceive
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
- <part name="summary">
<summary>Conflicting receive. Another receive activity or equivalent
(currently, onMessage branch in a pick activity) has already been enabled
with the partnerLink "Response", operation
name "onResult" and correlation set
"{{http://xmlns.oracle.com/Request/correlationset}
.
CorrProp={http://xmlns.oracle.com/Request/correlationset}CorrProp=45}" (or
conversation id).
.
Appendix A - Standard Faults in the BPEL 1.1 specification specifies a fault
should be thrown under these conditions.</summary>
</part>
</conflictingReceive>
</part>
.
But when the Receive activity is replaced with a Pick/onMessage activity, the second invoke
of onMessage does not result in a bpws:conflictingReceive fault. Instead, the instance is found in the Recovery Queue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms