OSB does not Propagate Internal Server HTTP 500 (Doc ID 1469660.1)

Last updated on AUGUST 12, 2024

Applies to:

Symptoms

When calling a business service that throws a SOAP Fault wrapped with an HTTP error code 500, OSB does not propagate this in tracing, instead it just throws a NullPointerException.

When hitting the external endpoint with SOAP UI, the SOAP Fault is clearly seen in the response body with the internal server error 500 in the header.   The error can be detected by analyzing the stack trace from the payload.

You can see the error from the OSB Test Console (this was done by analyzing the fault thrown by the error handler).

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.