502 Proxy Error 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 about Stack Overflow the company Business Learn more about hiring developers or 502 proxy error apache posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join
502 Proxy Error Dns Lookup Failure
the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes
502 Proxy Error Apache Error Reading From Remote Server
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 app on Tomcat 6 and Apache mod_proxy 2.2.3. Seeing a lot of 502 errors like this: Bad
502 Proxy Error Reason Error Reading From Remote Server
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 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 502 proxy error openshift 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 Apache is waiting for a response from Tomcat, there is no traffic flowing between Apache and the Browser (or whatever http client) - and so Apache closes down the connection to the browser. I found that if I left the Timeout setting at its default (300 seconds), then if the proxied re
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 and 502 proxy error apache reverse proxy 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
to fix that? The proxy server received an invalid http://www.webratio.com/forum/question-details/502-proxy-error?link=ln27d response from an upstream server. The proxy server could not handle http://blog.somepixels.net/en/502-proxy-error-uploading-from-apache-mod_proxy-to-tomcat-7/ 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 502 proxy 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 502 proxy error 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!API is. We're using mod_proxy to do the job and everything is hosted on Amazon's EC2. Everything was working perfectly, but sometime ago we've started to see some errors, when uploading big files, like this: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /app/api/upload. Reason: Error reading from remote server Apache/2.2.22 (Amazon) Server at our_app_server.com Port 443 We started looking for solutions to this problem and tried a lot of things, like configuring the timeout on Apache's httpd.conf: # Configuring the timeout Timeout 2400 ProxyTimeout 2400 # Configuring the reverse proxy ProxyPass /app http://localhost:8080/app ProxyPassReverse /app http://localhost:8080/app After we've changed the timeout, it got a little better, but didn't solve the problem completely. So, after a lot more googling, we found out that this error on Apache's log: (103)Software caused connection abort: proxy: pass request body failed is caused by a malformed server response and, to ignore it, we could set this option on our httpd.conf: ProxyBadHeader Ignore After this change, it finally revealed to us the real problem: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.web.multipart.MultipartException: Could not parse multipart servlet request; nested exception is org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. Read timed out org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:894) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789) javax.servlet.http.HttpServlet.service(HttpServlet.java:641) javax.servlet.http.HttpServlet.service(HttpServlet.java:722) org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:312) org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:116) org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:324) org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:324) We started looking for the solution again and found a interesting Tomcat setting called disableUploadTimeou