Reason Error Reading From Remote Server Tomcat
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 proxy error reading from remote server returned by apache more about Stack Overflow the company Business Learn more about hiring developers or posting 502 proxy error fix ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
The Proxy Server Received An Invalid Response From An Upstream Server. Apache Reverse Proxy
Overflow is a community of 6.2 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
Ah01102: Error Reading Status Line From Remote Server
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 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 502 proxy error apache reverse proxy 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 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
Error Reading From Remote Server Meaning
policies of this site About Us Learn more about Stack Overflow the proxybadheader ignore company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags bad gateway the proxy server received an invalid response from an upstream server. 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 http://stackoverflow.com/questions/169453/bad-gateway-502-error-with-apache-mod-proxy-and-tomcat takes a minute: Sign up Proxy Error 502 : The proxy server received an invalid response from an upstream server up vote 24 down vote favorite 7 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 http://stackoverflow.com/questions/20406845/proxy-error-502-the-proxy-server-received-an-invalid-response-from-an-upstream server received an invalid response from an upstream server. The proxy server could not handle the request GET /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 sor
Proxy Error The proxy server received an invalid response https://confluence.atlassian.com/confkb/proxy-error-when-viewing-the-content-indexing-page-389777939.html from an upstream server. The proxy server could not handle the request GET /admin/search-indexes.action. Reason: Error reading from remote server Apache/2.2.15 (CentOS) Server at confluence.com Port 80 Cause This error message triggered when an SSL connection is configured from the browser to Apache, and error reading Apache does a reverse proxy to your Tomcat server. Internet Explorersends the wrong host information in an SSL connection and confuses Apache VirtualHosts. In short, the server name presented is that of the reverse DNS resolution of the IP, not the one in the URL. from remote server Workaround There are three workarounds for this issue: Remove the reverse proxy Make a configuration where there's only one IP address per SSL virtual hosts/server name1 server name == 1 IP address == 1 certificate == 1 Apache Virtual Host Use a different browser References: Server Name Indication 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.