Intermittently a BPEL process consuming JMS messages fails with error, 'Java.lang.IllegalArgumentException: Context Of The Same RID' (Doc ID 2153485.1)

Last updated on JUNE 26, 2016

Applies to:

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

Symptoms

Scenario: A BPEL process is triggered by a JMS Adapter (queue consumer). The BPEL process also sends messages outbound to JMS in a request/reply pattern.

Intermittently a message is consumed, but the BPEL process fails with error below:

cube deliveryException not handled by the Collaxa Cube system.[[
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "java.lang.IllegalArgumentException: Context of the same RID, 1:1500739:3:17 already present in this family, 9ceac6e7-ca93-4d33-9dd5-83144d2827c6-04451bbf.
at
oracle.dms.context.internal.AbstractContextFamily.addContext(AbstractContextFamily.java:240)
at
oracle.dms.context.internal.wls.WLSContextManager.createAndActivateChildContext(WLSContextManager.java:1420)
at
oracle.dms.context.internal.wls.WLSContextManager.getContext(WLSContextManager.java:631)
at
oracle.dms.context.internal.wls.WLSContextManager.getContext(WLSContextManager.java:397)
at
oracle.dms.context.internal.wls.WLSContextManager.getContext(WLSContextManager.java:298)
at
oracle.dms.context.DMSContextManager.getContext(DMSContextManager.java:551)
An internal exception has not been properly handled by the server. Set the logging level for all loggers to debug, and resubmit your request again.  The server log should contain a more detailed exception report.

 

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