My Oracle Support Banner

User Unable to Get Application Error Code in OSB While Invoking an Adapter (Doc ID 965323.1)

Last updated on JUNE 29, 2022

Applies to:

Oracle Service Bus - Version 10.3 and later
Information in this document applies to any platform.


In OSB 10gR3 MP1, SOAP fault is not including actual failure details returned from called service.

In case of application error being received by adapter / business service, application error-code and error-details are not being included in the SOAP Fault and due to this applications are unable to perform proper error handling.

Generaic details are being populated in SOAP Fault like:

Fault: BEA-380001
Reason: Invoke JCA outbound service failed with application error.

For example a JCA Transport based business service currently returns the exception string in the SOAP fault detail. i.e. Fault: BEA-380001: Reason: Invoke JCA outbound service failed with application error.

But the underlying adapter log contains exception trace which contains useful data like 'ORA-XXXX"' error codes.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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