Created attachment 28781 [details] Error I'm Using Apache 2.2.16 and Tomcat 7.0.16. I have 3 Tomcat instance which executes 3 war files. To bypass the proxy I have configured httpd with 3 workers. 3 Tomcat instances are running in 8080, 8090, 8099. Intermittently I was getting 502 Proxy Error in 8090 and 8099 for all the POST operations. So I have set the below variables in the httpd.conf SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 After setting this configuration gradually the error rate got decreased but still we are facing some issues. When the request comes with HTTP/1.0 its working fine but when request comes in HTTP/1.1 I am getting 502 Proxy Error at some times. Please help me in resolving this issue. Thanks, Prakash S
- - [14/May/2012:13:43:30 +0300] "POST *** HTTP/1.0" 200 9324 - - [14/May/2012:13:43:36 +0300] "POST *** HTTP/1.0" 200 4572 - - [14/May/2012:13:43:49 +0300] "POST *** HTTP/1.1" 502 422 - - [14/May/2012:13:43:53 +0300] "POST *** HTTP/1.1" 200 1229
need error logs and packet captures of both sides of the connection to do anything on this.
Created attachment 29179 [details] Server Architecture Apache and Tomcat instances setup
Created attachment 29180 [details] httpd of Apache 2.2 Configuration made in Apache
Created attachment 29181 [details] Access lof with Failures and Errors Access lof with Failures and Errors
Created attachment 29182 [details] Error Descriptions Error log for the failures
I think now you could find out the issue clearly. if you need more details please get back to me. Waiting for your resolution
how about loglevel debug and packet captures?
I didn't get your question clearly. could you tell me how to capture the packets or should I change the loglevel to debug and capture the Packets?
Hi, I couldn't get your question, do I need to change the loglevel to debug and collect the packets? can you please explain me. Thanks, Prakash S
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.