Apache Error Reading Status Line From Remote Server
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the (20014)internal error proxy error reading status line from remote server workings and policies of this site About Us Learn more about Stack proxy-initial-not-pooled Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags error reading status line from remote server localhost Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how ah01102 error reading status line from remote server it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Intermittent error when using mod_proxy to do reverse proxy to SOAP service up vote 12 down vote favorite 5 I get this error every few minutes when using mod_proxy as a reverse proxy to a SOAP web service. There's
End Of File Found Proxy Error Reading Status Line From Remote Server
probably 3 or 4 requests going per seconds so we're talking around 1 or 2 out of every thousand that have this error. [Tue Nov 23 11:44:14 2010] [error] [client 172.16.1.31] (20014)Internal error: proxy: error reading status line from remote server soap1.server:8888 [Tue Nov 23 11:44:14 2010] [error] [client 172.16.1.31] proxy: Error reading from remote server returned by /someapp/path/to/web/service This causes the request to fail. If I have the client connect directly to the soap server without using the proxy, success is 100% so the problem appears to be in the proxy The configuration looks like this. The purpose is to switch to a backup server if the primary one is unavailable:
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
Ah00898: Error Reading From Remote Server Returned By
About Us Learn more about Stack Overflow the company Business Learn more about apache proxy-initial-not-pooled hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is (104)connection reset by peer: proxy: error reading status line from remote server a question 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 http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service answers are voted 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 http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de request GET /. My dilemma: 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://stackoverflow.com/questions/169453/bad-gateway-502-error-with-apache-mod-proxy-and-tomcat the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each error reading 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 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 from remote server 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 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 h