OSB - Unable to Receive Error Details for HTTP 404 Response in $fault or $body Context Variables from Remote REST Service
(Doc ID 1562529.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle Service Bus - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Symptoms
During a service callout to a REST back-end service from an OSB Proxy Service, the service returns an HTTP 404 response code, resulting in a BEA-382502 error. However, there are no details as to which HTTP error code was returned. Response details from $fault context variable are as follows:
According to OSB documentation when an error BEA-382502 is returned, the contents of the response, if any, can be seen in $fault message context variable. But even though there was a fault message sent from the back-end there was nothing seen in the $fault variable.
Oracle® Fusion Middleware Messages for Oracle Service Bus
11g Release 1 (11.1.1.6.3)
E15034-08
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e15034/TransformLoggables.html
|
BEA-382502 |
Error | OSB Service Callout action received an error response |
| Description | The service invoked by OSB Service Callout action has indicated that an error condition other than a SOAP fault has occured. For example, this may happen when an HTTP 404 (Page Not Found) error code is received from an external HTTP service. The contents of the received response (if any) can be seen in the details element of $fault message context variable. | |
| Action | Check the contents of response payload in $fault variable to see what the problem with service invocation is. |
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |