My Oracle Support Banner

Setting Correlation Id On Reply Fails with, 'correlationViolation' (Doc ID 1407986.1)

Last updated on APRIL 23, 2019

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


When attempting to run a BPEL process with the Setting Correlation id not initialized it cannot be used in a receiving activity so a Fault is thrown.

This can validated in the following scenario:

BPEL process has 2 sync calls that the client will call one after the other (Say Method 1, Method 2).

Method 1
Generate Corelation ID
Reply (set corelation initiate = Yes)

Method 2
Receive (set corelation initiate = No)
Reply (set corelation initiate = No)

In the above scenario, when invoking Method 2 the corelation id is not picked up at all.

A similar stacktrace can be found in the log files:

[soa_server1] [ERROR] [] [oracle.soa.bpel.engine] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid:<ECID>] [ BPELProcess1_pt] [APP: soa-infra]
[composite_name:CorelationTest] [component_name: BPELProcess1] [component_instance_id: 820085] [ fabric] [ bpelprocess1_client_ep]
[ soa-infra] This error contained the exceptions thrown by the underlying routing system. Root cause : [[ faultName: {{}correlationViolation}
messageType: {{}RuntimeFaultMessage}
at com.collaxa.cube.engine.ext.bpel.common.BPELWMPHelper.createCorrelationSet(BP
at com.collaxa.cube.engine.ext.common.ReceiveHandler.handleNormalInput(ReceiveHa
at com.collaxa.cube.engine.ext.common.ReceiveHandler.handle( 65)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELReceiveWMP.__executeStatement s(
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseB
at com.collaxa.cube.engine.CubeEngine._performActivity(
at com.collaxa.cube.engine.CubeEngine.performActivity(
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(
at com.collaxa.cube.engine.CubeEngine.endRequest(
at com.collaxa.cube.engine.CubeEngine.endRequest(
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(

[soa_server1] [NOTIFICATION] [][oracle.wsm.agent.WSMAgent] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid:<ECID>] [ BPELProcess1_pt] [APP: soa-infra]
[ fabric] [ bpelprocess1_client_ep] [ soa-infra] Message Type is normalized, exiting agent.processFault()

[soa_server1] [NOTIFICATION] [] [oracle.wsm.agent.WSMAgent] [tid: [ACTIVE].ExecuteThread: '2' for queue:'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [ BPELProcess1_pt] [APP: soa-infra]
[ fabric] [ bpelprocess1_client_ep] [ soa-infra]Message Type is normalized, exiting agent.processFault()

[soa_server1] [ERROR] [OWS-04086][oracle.webservices.service] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: soa-infra]
javax.xml.rpc.soap.SOAPFaultException: faultName:
[[messageType: {{}RuntimeFaultMessage}
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.generateSoapFaultException(
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(
at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(
at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricPr
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(


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

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