![]() ![]() : seproperties:se_runtime_properties> upstream_read_timeout Ĭhanging the value of the above-mentioned timeout options affects all the virtual services on the Service Engine.Įnable Age Out Idle Connections and change the value of Idle Durations using the Avi UI. : seproperties:se_runtime_properties> upstream_send_timeout : seproperties:se_runtime_properties> upstream_connect_timeout ![]() Use the se_runtime_properties option under the configure serviceengineproperties command. If the 1-hour timeout value (wait time) for the HTTP 504 response code is not acceptable, follow one of the workarounds mentioned below:Ĭhange the value of the following timeout options to reduce the HTTP 504 response code wait time using the Avi shell prompt. To know more about the above-mentioned timeout values, refer to FAQ on the different timeout options on an Avi Service Engine. The timeout value for the idle connections on an Avi SE can be changed using the Avi shell prompt. The default values for the upstream_send_timeout and the upstream_read_timeout is 3600000 ms (1 hour). The parameter upstream_connect_timeout is the idle timeout for back-end connection, and the default value for this timeout is 3600000 ms (1 hour). The reason for the long default idle timeout is that the client or the application server would close out the connection in the case of an error. The Avi SE waits for a response untill the read timeout ( 1 hour), and responds to the client with a response code 504. ResolutionĪvi Vantage responds with an HTTP 504 error code when a back-end server is up, and the Avi Service Engine is able to send the request to the back-end server, but the server goes down before it can respond. HTTP 504 response code is observed on Avi Vantage for HTTP requests. HTTP 504 Response Code is Observed on Avi Vantage Issue & Symptoms ![]()
0 Comments
Leave a Reply. |