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 11.1.1.5.0 and later
Information in this document applies to any platform.

Symptoms

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
Receive
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>] [WEBSERVICE_PORT.name: BPELProcess1_pt] [APP: soa-infra]
[composite_name:CorelationTest] [component_name: BPELProcess1] [component_instance_id: 820085] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: bpelprocess1_client_ep]
[J2EE_APP.name: soa-infra] This error contained the exceptions thrown by the underlying routing system. Root cause : [[
com.oracle.bpel.client.BPELFault: faultName: {{http://docs.oasis-open.org/wsbpel/2.0/process/executable}correlationViolation}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
at com.collaxa.cube.engine.ext.bpel.common.BPELWMPHelper.createCorrelationSet(BP ELWMPHelper.java:1874)
at com.collaxa.cube.engine.ext.common.ReceiveHandler.handleNormalInput(ReceiveHa ndler.java:208)
at com.collaxa.cube.engine.ext.common.ReceiveHandler.handle(ReceiveHandler.java: 65)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELReceiveWMP.__executeStatement s(BPELReceiveWMP.java:210)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseB PELActivityWMP.java:158)
at com.collaxa.cube.engine.CubeEngine._performActivity(CubeEngine.java:2463)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2334)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1115)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4350)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4281)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:679)
...

[soa_server1] [NOTIFICATION] [][oracle.wsm.agent.WSMAgent] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid:<ECID>] [WEBSERVICE_PORT.name: BPELProcess1_pt] [APP: soa-infra]
[J2EE_MODULE.name: fabric] [WEBSERVICE.name: bpelprocess1_client_ep] [J2EE_APP.name: 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>] [WEBSERVICE_PORT.name: BPELProcess1_pt] [APP: soa-infra]
[J2EE_MODULE.name: fabric] [WEBSERVICE.name: bpelprocess1_client_ep] [J2EE_APP.name: 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:
{{http://docs.oasis-open.org/wsbpel/2.0/process/executable}correlationViolation}
[[messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.generateSoapFaultException(WebServiceEntryBindingComponent.java:1053)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(WebServiceEntryBindingComponent.java:890)
at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(FabricProvider.java:113)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1081)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:232)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:192)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:459)
at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricPr oviderServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
...

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.