Unit Test Exception With Direct Binding With Asynchronous Callback (Doc ID 1175545.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Symptoms

Whenever the test framework (Unit test) is used as a client for invoking asynchronous services of a composite configured with Direct binding , the execution of the component fails with the exception 'The service path "null" is invalid', while receiving the callback.

When running the test from the Enterprise Manager console, the unit test indicators report that the test completes successfully. However, when you view the composite instance flow trace, we find that the BPEL instance is actually faulted when attempting the callback invocation with the following error message:

<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary" >
<summary>oracle.fabric.common.FabricInvocationException: java.lang.IllegalArgumentException: The service path "null" is invalid</summary>
</part>
<part name="detail" >
<detail>The service path "null" is invalid</detail>
</part>
<part name="code" >
<code>null</code>
</part>
</remoteFault>
</bpelFault>

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