My Oracle Support Banner

Intermittent Errors "503 service unavailable"/"504 Gateway Timeout" While Calling SOAP/REST Service for Inventory Transactions (Doc ID 2591718.1)

Last updated on OCTOBER 02, 2019

Applies to:

Oracle Fusion Inventory Management Cloud Service - Version and later
Oracle Fusion Inventory Management - Version and later
Information in this document applies to any platform.


Intermittent failures to call SOAP service in this issue TransactionManagerServiceV2 or REST service.
The connections are configured with each of the SOAP/REST service and then being called/invoked from inside a integration service.
There is no particular time for the issue occurrence. Most of the transactions went fine using the services but some fail intermittently.
There is no pattern for such error occurrence.

SOAP service
The complete error details is: Error while dispatching SOAP message to the endpoint javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable from url ===== reqeust ======== Content-Type:text/xml; charset=UTF-8 Content-Length:3707 SOAPAction:"" Authorization:***hidden***

REST service
The complete error details is:

Fault Details : <ns2:APIInvocationError
<ns2:errorPath><![CDATA[POST returned a response
request status of 504 Gateway
<TITLE>Gateway Timeout - In read </TITLE> </HEAD><BODY> <H1>Gateway
Id: 33353930323239313136383739373437
Timeout</H1> The proxy server did not receive a timely response from the
upstream server.<P>
Instance ID  :  11111111
Reference #1.111111a1.11111111111.1a2b3cd
</BODY></HTML> .A 504 Gateway Timeout indicates that the proxy/edge server
did not get a response
from the upstream/origin server in a given time window. This condition could
be realized when the origin server is
down or not working properly. This is usually a temporary condition. You can
trace the cURL representation of the
request sent to the target service from the Oracle Integration Cloud server
logs. Try invoking the target service
using cURL. If the problem persists, contact the target service admin.
</ns2:APIInvocationError> :Application Error

The issue can be reproduced at will with the following steps:
1. Web-service TransactionManagerServiceV2 is called from external integration service
2. Intermittently the web-service call fails with following error seen in the messages.
3. Same transaction gets successful if retried again through SOAPUI




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.