Last updated on JUNE 25, 2017
Applies to:Oracle WebLogic Server - Version 10.3.4 to 10.3.5
Oracle Service Bus - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11g]
Information in this document applies to any platform.
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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms