502 Proxy Error Apache Timeout
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
502 Proxy Error Apache Error Reading From Remote Server
about Stack Overflow the company Business Learn more about hiring developers or posting ads 502 proxy error apache reverse proxy with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack 502 proxy error dns lookup failure Overflow is a community of 4.7 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
502 Proxy Error Reason Error Reading From Remote Server
down vote favorite 14 We're running a web 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
502 Proxy Error Openshift
plenty of threads, so it's not thread-constrained. We're pushing 2400 users via 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 Pro
Start 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 502 proxy error chrome Learn more about Stack Overflow the company Business Learn more about hiring developers
502 Proxy Error Web Service
or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question 502 proxy error amazon and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted http://stackoverflow.com/questions/169453/bad-gateway-502-error-with-apache-mod-proxy-and-tomcat up and rise to the top Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 (Debian) mod_proxy and Jetty 6.1.18 up vote 46 down vote favorite 22 Apache is receiving requests at port :80 and proxying them to Jetty at port :8080 The proxy server received an invalid response from an upstream server The proxy server could not handle the request GET /. My dilemma: http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de Everything works fine normally (fast requests, few seconds or few tens of seconds long requests are processed ok). Problems occur when request processing takes long (few minutes?). If I issue request instead directly to Jetty at port :8080 the request is processed OK. So problem is likely to sit somewhere between Apache and Jetty where I am using mod_proxy. How to solve this? I have already tried some "tricks" related to KeepAlive settings, without luck. Here is my current configuration, any suggestions? #keepalive Off ## I have tried this, does not help #SetEnv force-proxy-request-1.0 1 ## I have tried this, does not help #SetEnv proxy-nokeepalive 1 ## I have tried this, does not help #SetEnv proxy-initial-not-pooled 1 ## I have tried this, does not help KeepAlive 20 ## I have tried this, does not help KeepAliveTimeout 600 ## I have tried this, does not help ProxyTimeout 600 ## I have tried this, does not help NameVirtualHost *:80
providing any support for the steps described on this page. Please be aware https://confluence.atlassian.com/confkb/occasional-502-bad-gateway-from-apache-http-proxy-200212803.html that this material is provided for your information only, and http://www.webratio.com/forum/question-details/502-proxy-error?link=ln27d that you use it at your own risk. Problem Users will occasionally receive an 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 502 proxy 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 502 proxy error 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.
to fix that? The proxy server received an invalid response from an upstream server. The proxy server could not handle the requestGET/. Reason:Error reading from remote server
x 0 Follow Answer Answer at this question and get points! 3 Answers most voted oldest newest 05 Feb '15, 07:26 AM Laurentiu Radu Forum Starter - Level 2 Hi, This error typically appearswhen Apache web server does not receive a valid HTTP response from the upstream server, which in this case is your Tomcat web application. If you are not using Apache HTTP Server and your are using only Tomcat the error may be generated due the following reasons: The Tomcat threads are timing out A network device is blocking the request, perhaps as some sort of connection timeout or DoS attack prevention system, or maybe a firewalll Tomcat may have crashed If you are using Apache, the solution is simple. Just edit thehttpd.conf file increasing the Timeout and ProxyTimeout values and adding theProxyBadHeader parameter. Timeout 3000 ProxyTimeout 3000 ProxyBadHeader Ignore More information you can find on Apache website (http://httpd.apache.org/docs/2.2/mod/mod_proxy.html) Also, please tell us in which configuration this error apears (Apache-Tomcat, only Tomcat,Nginx-Tomcat, etc.) x 0 05 Feb '15, 08:04 AM jisu lim No Forum Badges Thank you for your answer soon. I just deployed my project on the cloud. x 0 10 Mar '15, 02:51 PM Alexander Marquez No Forum Badges hola tengo el mismo erro pero no tengo instalado apache, como valido el log de webratio? x 0 Your answer Answer at this question and get points!