Hi,
I get a 504 Gateway Timeout error every few hundred requests while running my tests. Please see the response below. The requests have nothing special about them to get this error. I feel like this is on the NeoLoad side and not my server. Please suggest any ways that I can may be retry when this error happens, or atleast ignore this error so that my test doesn't fail upon this error.
<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.4.6 (Ubuntu)</center>
</body>
</html>
This mostly likely is a network error between the servers involved. I doubt this has anything to do with Neoload itself.
The NGnix-based gateway between the Load Generator and your tested application raises time-outs.
504 means that the time-out is raised when the gateway waits too long from the tested server. It means your Server is overloaded.
What is typical in such situation: getting not too bad average response time but higher max time. If all requests are impacted, it's a general issue that may be related to the number of parralel connections accepted by the server (available Threads/Workers on Apache). If only a few requests are impact, then it's related to something more specific and business related (ex: long database query).
christophe answered
Sulav answered
Harv posted a new question
