This content has been marked as final. Show 2 replies
I think this means you have found a problem with either the web application. This web site explains why a 504 might occur:
It might be that your web application is making requests to other app servers that might be running slow. Try adding some ServerStats for all the machines that are involved in your web application. You might be able to correlate some of the errors with performance problems on those servers.
Thanks for the link. Like you, I also suspect it is a problem on either the web application server, or some network piece in between. So it's good we found it. But now we need to know where it is occuring. So now I have a couple more questions I hope you or someone can answer.
I want to rule out my workstation (the one running eload). Has anyone recieved a 504 and had the problem be with the eload server itself and not a problem with the actual application being tested or the app server it is running on?
Does anyone have tips on how they narrowed the 504 down from here? Even though the problem is likely on one of the servers or something in the network - and isn't a problem specific to Empirix - I suspect others have also detected problems in their infrastructure when running eload. Any experiences or suggestions to help pinpoint where? We had performance monitoring on the web app servers. I found an article on this site recommending what to monitor - and I've passed it on to the web app server admins to reference before our next attempt.