SOA 11g: Invoke (webservice) - Some Exceptions are not Propagate to the Catch All (Doc ID 1562841.1)

Last updated on MARCH 27, 2019

Applies to:

Symptoms

The problem is the following :
- If an incorrect endpoint URI is supplied to an invoke, the catch all of the scope is triggered and the error can be handled.
- If a malformed endpoint URI is supplied, the catch all is not triggered and the BPEL process continues its execution as if it had reached the service and received the response (which is not the case).

If the catch all is triggered, a response with "catch executed." is received,  otherwise an empty response is received.

Example:
- "http://<HOST>:<PORT>/test", the catch all will be triggered and get "Catch executed."
- "htp://<HOST>:<PORT>/test", the catch will NOT be triggered and the BPEL will process "correctly" (empty response)

Changes

Cause

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