My Oracle Support Banner

Correlation with signal events is throwing an error when the second instance is created, 'Conflicting receive' (Doc ID 2162838.1)

Last updated on MAY 10, 2023

Applies to:

Oracle Business Process Management Suite - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

When creating a second instance of a process that has a signal within an event subprocess, the following exception is thrown:

Caused By: com.oracle.bpel.client.BPELFault: faultName:
{{http://schemas.xmlsoap.org/ws/2003/03/business-process/}conflictingReceive}messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
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 "", operation name
"{http://xmlns.oracle.com/AddToXSDArray/OracleBPM12cEventSubProcessDemo/OrderEventDefinition}cancelEvent" and correlation set
"{{http://xmlns.oracle.com/bpmn/bpmnProcess/OracleBPM12cEventSubProcessDemo}orderId={http://xmlns.oracle.com/bpmn/bpmnProcess/OracleBPM12cEventSubProcessDemo}orderId=}" (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.
}
.
at com.collaxa.cube.engine.ext.common.ReceiveHandler.handleEDNInput(ReceiveHandler.java:156)
at com.collaxa.cube.engine.ext.common.ReceiveHandler.handle(ReceiveHandler.java:73)
at oracle.bpm.bpmn.engine.model.runtime.microinstructions.MIReceive.doExecute(MIReceive.java:58)
at oracle.bpm.bpmn.engine.microkernel.MIBase.execute(MIBase.java:34)
at oracle.bpm.bpmn.engine.microkernel.MISequenceBlock.doExecute(MISequenceBlock.java:68)
at oracle.bpm.bpmn.engine.microkernel.MIBase.execute(MIBase.java:34)
at oracle.bpm.bpmn.engine.microkernel.MicroInstructionContext.callMicroInstruction(MicroInstructionContext.java:205)
at oracle.bpm.bpmn.engine.microkernel.MICall.doExecute(MICall.java:38)
at oracle.bpm.bpmn.engine.microkernel.MIBase.execute(MIBase.java:34)
at oracle.bpm.bpmn.engine.microkernel.MISequenceBlock.doExecute(MISequenceBlock.java:68)
at oracle.bpm.bpmn.engine.microkernel.MIBase.execute(MIBase.java:34)
at oracle.bpm.bpmn.engine.microkernel.MicroInstructionContext.callMicroInstruction(MicroInstructionContext.java:205)
at oracle.bpm.bpmn.engine.microkernel.MicroInstructionContext.callProcedure(MicroInstructionContext.java:212)
at oracle.bpm.bpmn.engine.microkernel.MicroInstructionContext.executeProcedure(MicroInstructionContext.java:335)
at oracle.bpm.bpmn.engine.model.runtime.MIBPMNActivityWMP.executeProcedure(MIBPMNActivityWMP.java:257)
at oracle.bpm.bpmn.engine.model.runtime.MIBPMNActivityWMP.__executeStatements(MIBPMNActivityWMP.java:222)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:188)

 

 

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.