SSLClientChannel[C:XX.XX.XX.XX:443 useCount=2 bytesRead=0īytesWritten=824 age=55458ms lastIO=55000ms. 20:16:57,361 org:myorg env:staging api:profileNewsletters ERROR HTTP.CLIENT - HTTPClient$Context$3.onTimeout() : 20:16:54,340 org:myorg env:staging api:profiles rev:13 - AbstractResponseListener.onException() Gateway Sample Message Processor log showing Gateway Timeout Error If you find Gateway Timeout and onTimeoutRead errors for the specific API proxy requestĪt the specific time, then it indicates that the Message Processor has timed out. ( /opt/apigee/var/log/edge-message-processor/logs/system.log) Procedure #2 Using Message Processor logs Note: Only Private Cloud users can perform these steps. In the above trace, the Message Processor times out after 55002 ms as the backend server does The following provides a sample Trace showing that the backend server did not respond evenĪfter 55 seconds resulting in a 504 Gateway Timeout error:
#UP THE NGINX GATEWAY TIMEOUT CODE#
Once the error has occurred, examine the specific request which shows the response code as.
Either wait for the error to occur or if you have theĪPI call, then make some API calls and reproduce the 504 Gateway Timeout error. If the issue is still active ( 504 errors are still happening), then follow the below Procedure #1 Using Trace Note: Both Private and Public Cloud users can perform these You can use the following procedures to diagnose if the 504 Gateway Timeout error has occurredīecause of the slow backend server. Message Processor times out before backend server responds Diagnosis
#UP THE NGINX GATEWAY TIMEOUT HOW TO#
The following sections describe how to diagnose and resolve the issue under each of these Client application times out before Router/Message Processor/backend server responds.Router times out before Message Processor/backend server responds.Message Processor times out before backend server responds.Occur under one of the following scenarios: As explained in the section above, the timeout can You will get a 504 Gateway Timeout error. If the backend server is very slow or takes a long time to process the API request, then The backend server that is processing the API request is too slow due to high load orĮdge takes a long time to process the API request due to high load or poor In Edge, the typical causes for 504 Gateway Timeout error are: Cause The Client application times out and ends the response status as 504.Router does not respond to the client application within the specified timeout.Router times out and sends the response status as 504 Gateway.Message Processor does not respond to the router within the specified timeout.Message Processor times out and sends the response status as 504 Gateway.Backend server does not respond to the Message Processor within a specified timeout.The following table provides more details about when timeouts may occur in Edge: Timeout occurrence The specified period of time, then 504 Gateway Timeout Error is returned. Of time for every API request based on the timeout values. The Edge platform expects a response to be sent within a certain period The client application, routers, and Message Processors within Edge platform are set up with > Message Processor -> Backend Server as shown in the below figure: Typical path for an API request via the Edge platform will be Client -> Router
In some cases, the following error message may also be observed: The HTTP status code - 504 Gateway Timeout error indicates that the clientĭid not receive a timely response from the Edge Gateway or backend server during the execution ofĬlient application gets the following response code: HTTP/1.1 504 Gateway Timeout Gateway Timeout as a response for the API calls. The client application receives an HTTP status code of 504 with the message Note: Was this troubleshooting playbook helpful? Please let us know You're viewing Apigee Edge documentation.
0 kommentar(er)
