OIC Integration Using DBAdapter Sporadically Failing With Error "HTTP 504 Gateway Time-out" (Doc ID 2698592.1)

Last updated on AUGUST 07, 2020

Applies to:

Symptoms

ISSUE

-----------

In production environment, sporadically transactions to database calls failing with below error in the logs.

ERROR
-----------------------

ServerLog:

[2020-08-03T11:50:20.843+00:00] [oiciad5I_server_1] [ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '171' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <user>] [ecid: 22f3870b-25ab-47d6-9dfd-ea8b6b3b3bac-0102eee4,1:183307:32] [partition-name: DOMAIN] [tenant-name: GLOBAL] [oracle.soa.tracking.FlowId: 35709352] [oracle.soa.tracking.InstanceId: 2640774] [oracle.soa.tracking.SCAEntityId: 300245] [composite_name: <instance>!01.00.0000] [FlowId: 0000NEoA7QyCcpW_xxo2yW1UsOGT000^AM] Response cannot be handled by the Generic REST adapter.Fault Details : [[
<nstrgdfl:APIInvocationError xmlns:nstrgdfl="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/LogStartMsg"><nstrgdfl:type/><nstrgdfl:title/><nstrgdfl:detail/><nstrgdfl:errorCode/><nstrgdfl:errorDetails><nstrgdfl:type>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.5</nstrgdfl:type><nstrgdfl:title>Gateway Timeout</nstrgdfl:title><nstrgdfl:errorCode>504</nstrgdfl:errorCode><nstrgdfl:errorPath>&lt;![CDATA[POST https://<instance>.integration.ocp.oraclecloud.com/ic/api/integration/v1/flows/rest/CIF_DB_ADAPTER_SERVICE/1.0/metadata/cif/input returned a response status of 504 Gateway Timeout]]&gt;</nstrgdfl:errorPath><nstrgdfl:instance>&lt;![CDATA[&lt;html&gt;&#13;
&lt;head&gt;&lt;title&gt;504 Gateway Time-out&lt;/title&gt;&lt;/head&gt;&#13;
&lt;body bgcolor="white"&gt;&#13;
&lt;center&gt;&lt;h1&gt;504 Gateway Time-out&lt;/h1&gt;&lt;/center&gt;&#13;
&lt;hr&gt;&lt;center&gt;&lt;/center&gt;&#13;
&lt;/body&gt;&#13;
&lt;/html&gt;&#13;
.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. ]]&gt;</nstrgdfl:instance></nstrgdfl:errorDetails></nstrgdfl:APIInvocationError> oracle.cloud.connector.api.RemoteApplicationException: Fault Details :
<nstrgdfl:APIInvocationError xmlns:nstrgdfl="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/LogStartMsg"><nstrgdfl:type/><nstrgdfl:title/><nstrgdfl:detail/><nstrgdfl:errorCode/><nstrgdfl:errorDetails><nstrgdfl:type>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.5</nstrgdfl:type><nstrgdfl:title>Gateway Timeout</nstrgdfl:title><nstrgdfl:errorCode>504</nstrgdfl:errorCode><nstrgdfl:errorPath>&lt;![CDATA[POST https://<instance>.integration.ocp.oraclecloud.com/ic/api/integration/v1/flows/rest/CIF_DB_ADAPTER_SERVICE/1.0/metadata/cif/input returned a response status of 504 Gateway Timeout]]&gt;</nstrgdfl:errorPath><nstrgdfl:instance>&lt;![CDATA[&lt;html&gt;&#13;
&lt;head&gt;&lt;title&gt;504 Gateway Time-out&lt;/title&gt;&lt;/head&gt;&#13;
&lt;body bgcolor="white"&gt;&#13;
&lt;center&gt;&lt;h1&gt;504 Gateway Time-out&lt;/h1&gt;&lt;/center&gt;&#13;
&lt;hr&gt;&lt;center&gt;&lt;/center&gt;&#13;
&lt;/body&gt;&#13;
&lt;/html&gt;&#13;
.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. ]]&gt;</nstrgdfl:instance></nstrgdfl:errorDetails></nstrgdfl:APIInvocationError>
    at oracle.cloud.connector.impl.RESTFaultGenerator.errorResponseException(RESTFaultGenerator.java:217)
    at oracle.cloud.connector.impl.RESTEndpoint.handleHttpResponse(RESTEndpoint.java:987)
    at oracle.cloud.connector.impl.RESTEndpoint.createResponseMessage(RESTEndpoint.java:741)
    at oracle.cloud.connector.impl.RESTEndpoint.invoke(RESTEndpoint.java:230)
    at oracle.cloud.connector.impl.LoggingAwareRESTEndpoint.invoke(LoggingAwareRESTEndpoint.java:58)
    at oracle.cloud.connector.impl.CloudOperationImpl.invoke(CloudOperationImpl.java:122)
    at oracle.tip.adapter.cloud.CloudAdapterInteraction.sendMessageToCloudProvider(CloudAdapterInteraction.java:448)
    at oracle.tip.adapter.cloud.CloudAdapterInteraction.execute(CloudAdapterInteraction.java:172)

Agent Log:
[2020-08-04T11:05:43.126Z] [SEVERE] [ThreadID: 15] [Logger: oracle.cloud.cpi.agent.SyncService] [SRC Class: oracle.cloud.cpi.agent.SyncService; Method: getIntegrationMetadata] Unable to fetch activation artifacts metadata. javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out
at org.glassfish.jersey.client.JerseyInvocation.createExceptionForFamily(JerseyInvocation.java:1125)
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1105)
at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:883)
at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$1(JerseyInvocation.java:767)
at org.glassfish.jersey.internal.Errors.process(Errors.java:316)
at org.glassfish.jersey.internal.Errors.process(Errors.java:298)
 
 

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.