Bad Gateway Error Apache
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the apache 502 bad gateway company Business Learn more about hiring developers or posting ads with us Stack Overflow 502 bad gateway apache reverse proxy Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 apache tomcat bad gateway million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Bad Gateway 502 error with Apache mod_proxy and Tomcat up vote 39 down vote favorite 14 We're running a web cydia bad gateway error app on Tomcat 6 and Apache mod_proxy 2.2.3. Seeing a lot of 502 errors like this: Bad Gateway! The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /the/page.do. Reason: Error reading from remote server If you think this is a server error, please contact the webmaster. Error 502 Tomcat has plenty of threads, so it's not thread-constrained. We're pushing 2400 users via
Bad Gateway Error 502 Citrix
JMeter against the app. All the boxes are sitting inside our firewall on a fast unloaded network, so there shouldn't be any network problems. Anyone have any suggestions for things to look at or try? We're heading to tcpdump next. UPDATE 10/21/08: Still haven't figured this out. Seeing only a very small number of these under load. The answers below haven't provided any magical answers...yet. :) java apache tomcat mod-proxy share|improve this question edited Oct 21 '08 at 19:45 community wiki 2 revsAlex Miller I am facing this problem for some time during my running application –Uday A. Navapara Mar 12 '15 at 5:27 add a comment| 7 Answers 7 active oldest votes up vote 32 down vote Just to add some specific settings, I had a similar setup (with Apache 2.0.63 reverse proxying onto Tomcat 5.0.27). For certain URLs the Tomcat server could take perhaps 20 minutes to return a page. I ended up modifying the following settings in the Apache configuration file to prevent it from timing out with its proxy operation (with a large over-spill factor in case Tomcat took longer to return a page): Timeout 5400 ProxyTimeout 5400 Some backgound ProxyTimeout alone wasn't enough. Looking at the documentation for Timeout I'm guessing (I'm not sure) that this is because while Apach
providing any support for the steps described on this page. Please be aware
Please Explain This 502 Bad Gateway Error
that this material is provided for your information only, and 502 bad gateway error nginx that you use it at your own risk. Problem Users will occasionally receive an apache 502 proxy error error page reporting a "Bad gateway" condition. This means the proxy couldn't get a response from the application server. Cause This can result from http://stackoverflow.com/questions/169453/bad-gateway-502-error-with-apache-mod-proxy-and-tomcat a known issue in Apache, affecting versions 2.0.63 through to 2.2.3, and was marked as resolved with 2.2.4. Apache wasn't checking for one of the possible conditions for its connections to the application server, so would periodically (e.g. once in tens of thousands of requests) use a https://confluence.atlassian.com/confkb/occasional-502-bad-gateway-from-apache-http-proxy-200212803.html connection handle that had been reset by the application server. Resolution Upgrade to the latest version of Apache httpd. If you're using a web server compiled from source and have a strong reason not to upgrade, you also have the option of making a tiny edit to the source as described in one of the comments and recompiling. Was this helpful? Yes No Thanks for your feedback! Why was this unhelpful? It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © 2016 Atlassian Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
contribution towards the costs, the time and effort that's going in this site and building. Thank You! Steffen Apache https://www.apachelounge.com/viewtopic.php?p=25244 Lounge is not sponsored by anyone.Your donations will help to keep this site alive and well, and continuing the building of the binaries. Randomly receive 502 Bad Gateway error (Apache 2.4.4) Apache Forum Index -> Apache View previous topic :: View next topic Author Message hyohannesJoined: 23 Jul 2013Posts: 4Location: USA, Boston Posted: bad gateway Tue 23 Jul '13 22:08 Post subject: Randomly receive 502 Bad Gateway error (Apache 2.4.4) Hello all, I am currently running apache 2.4.4 with Tomcat and randomly i receive the following error when i try to hit the external URL: Bad Gateway The proxy server received an invalid response from an upstream server ==================================================== Inside apachie bad gateway error error.log file., i also see the following error, i am not sure if they are related: "The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed." ===================================================== Here is my httpd.conf file: Admin note: Removed the httpd.conf, see forum rules to use paste bin. ================================================= Any possible pointers or tips will be greatly appreciated. Thanks, -Hab Back to top hyohannesJoined: 23 Jul 2013Posts: 4Location: USA, Boston Posted: Tue 23 Jul '13 22:43 Post subject: Here is httpd.conf file. I hope i posted this time properly. Admin note: Sorry, please read the forum rules, Rule 0. Back to top SteffenModeratorJoined: 15 Oct 2005Posts: 2406Location: Hilversum, NL, EU Posted: Wed 24 Jul '13 12:52 Post subject: winnt_accept: Asynchronous AcceptEx failed: be sure you have in your httpd.conf AcceptFilter http none AcceptFilter https none EnableSendfile off EnableMMAP off Steffen Back to top hyohannesJoined: 23 Jul 2013Posts: 4Location: USA, Boston Posted: Wed 24 Jul '13 14:52 Post subject: Thanks Steffen. It seems I don't see the err