Proxy Error Reading From Remote Server Returned B
Contents |
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 Learn more about Stack Overflow the company Business (20014)internal error: proxy: error reading status line from remote server Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users apache error reading status line from remote server Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes ah00898: error reading from remote server returned by a minute: Sign up Here's how 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 (104)connection reset by peer: proxy: error reading status line from remote server service up vote 13 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 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]
Proxy-initial-not-pooled
[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
Error Reading Status Line From Remote Server Localhost
About Us Learn more about Stack Overflow the company Business Learn more about hiring setenv proxy-nokeepalive 1 developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a setenv proxy-initial-not-pooled 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 answers http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service are voted up and rise to the top Apache as proxy generates failure. up vote 2 down vote favorite 1 We are using apache proxy to enable our application servers to reach specific web sites over the internet. The setup is as follows: application servers --> apache proxy --> Internet website Some of the requests fail with the below error in the application server log:
http://serverfault.com/questions/509230/apache-as-proxy-generates-failureProxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST nbsp;/link.
Reason: Error reading from remote server
and the below debug log in the apache error.log file: [Mon May 20 09:57:54 2013] [debug] mod_proxy_http.c(56): proxy: HTTP: canonicalising URL //myURL.com [Mon May 20 09:57:54 2013] [debug] proxy_util.c(1506): [client 172.20.101.71] proxy: https: found worker `https://myurl.com/` for `https://myurl.com/link` [Mon May 20 09:57:54 2013] [debug] mod_proxy.c(1015): Running scheme https handler (attempt 0) [Mon May 20 09:57:54 2013] [debug] mod_proxy_http.c(1973): proxy: HTTP: serving URL https://myurl.com/link [Mon May 20 09:57:54 2013] [debug] proxy_util.c(2011): proxy: HTTPS: has acquired connection for (mu=y url) [Mon May 20 09:57:54 2013] [debug] ssl_engine_io.c(1908): OpenSSL: I/O error, 5 bytes expected to read on BIO#136e90 [mem: 190593] [Mon May 20 09:57:54 2013] [debug] proxy_util.c(2067): proxy: connecting https://myurl.com/link to myurl.com:443 [Mon May 20 09:57:54 2013] [debug] proxy_util.c(2193): proxy: connected /link to myurl.com:443 [Mon May 20 09:57:54 2013] [debug] ssl_engine_io.c(1908): OpenSSL: I/O error, 5 bytes expected to read on BIO#136e90 [mem: 190593] [Mon May 20 09:57:54 2013] [info] [client ip] (131)Connection reset by peer: SSL input filter read failed. [Mon May 20 09:57:54 2013here 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 http://stackoverflow.com/questions/20406845/proxy-error-502-the-proxy-server-received-an-invalid-response-from-an-upstream 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 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Proxy Error 502 : The proxy server error reading received an invalid response from an upstream server up vote 24 down vote favorite 6 We are building a mass mailing sending application in Java. Mail is being send by third party SMTP. After sending 400-500 mails tomcat6 service get stopped. Below is the error. Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET from remote server /lin/Campaignn.jsp. Reason: Error reading from remote server Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request. Apache Server at msizzler.com Port 80 But when we are sending from localhost I did not received any error. It send all the mails. Please help me to sort it out this problem. java email proxy tomcat6 share|improve this question asked Dec 5 '13 at 17:36 Ranjeet Ranjan 1332210 add a comment| 3 Answers 3 active oldest votes up vote 26 down vote The HTTP 502 "Bad Gateway" response is generated when Apache web server does not receive a valid HTTP response from the upstream server, which in this case is your Tomcat web application. Some reasons why this might happen: Tomcat may have crashed The web application did not respond in time and the request from Apache timed out 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 If the problem is related to timeout settings, you may be able to resolve it by investigating the following: ProxyTimeout directive of Apache's mod_proxy Connector config of Apache Tomcat