Re: [users@httpd] a lot of 502 error with using mod_proxy_http after upgrading tomcat
Hi, Thank you for your reply. > Did you test tomcat alone after the upgrade? Was it working as expected or was it just showing weirdness? I would start from there :) > I didn't try tomcat only. But we use a lot of rewrite rules with httpd, so that we cannot test easily... Moreover, the errors sometimes occur, sometimes not... > My suggestion would be to check https://tomcat.apache.org/tomcat-7.0-doc/changelog.html for changes between the two versions that you > mentioned to find anything that could have changed Tomcat's behavior. > I also think this would be a better way. We try to test and isolate the problem to use various versions of tomcat. Thank you. 2016-03-11 18:07 GMT+09:00 Luca Toscano <toscano.l...@gmail.com>: > Hi! > > 2016-03-11 5:18 GMT+01:00 Kenichi MASUDA <masu...@gmail.com>: >> >> >> httpd log say that "proxy: Error reading from remote server returned by" >> > > This error is usually not httpd's fault, but something wrong thrown by the > proxied host (that can be from TCP connection reset to HTTP > malformed/garbage IIRC). > > >> I downgraded tomcat to 7.0.39-1, so that these errors disappeared. >> > > My suggestion would be to check > https://tomcat.apache.org/tomcat-7.0-doc/changelog.html for changes > between the two versions that you mentioned to find anything that could > have changed Tomcat's behavior. > > >> Is there any way or solution to trace this situation? >> > > Did you test tomcat alone after the upgrade? Was it working as expected or > was it just showing weirdness? I would start from there :) > > Luca > > -- mailto:masu...@gmail.com
[users@httpd] a lot of 502 error with using mod_proxy_http after upgrading tomcat
Hi,
I posted the tomcat-users mailing list about my situation, so I was
recommended to post httpd-user mailing list,
so that I ask here too (I apologize for posting like multi-post).
Our system is httpd and tomcat, and a client sends a request to httpd which
listens as 80, after that httpd throw it like this to the tomcat which
exists in backend and serves as 8080 port with the rewrite rule though,
RewriteCond %{REQUEST_URI}
!\.(png|jpe?g|gif|css|js|xml|json|jsonp|ico|html?|swf|txt)$
RewriteRule ^/(.*)$ http://localhost:8080/core/$1 [P,L]
these errors were occurred after upgrading tomcat from 7.0.39-1 to 7.0.68-1.
httpd log say that "proxy: Error reading from remote server returned by"
and
a client say that "502 proxy error. The proxy server received an invalid
response from an upstream server. The proxy server could not handle the
request POST /foo/bar"
I downgraded tomcat to 7.0.39-1, so that these errors disappeared.
Is there any way or solution to trace this situation?
Is there anyone know or encounter this error?
--
mailto:masu...@gmail.com
