https://issues.apache.org/bugzilla/show_bug.cgi?id=57520
--- Comment #9 from dk <[email protected]> --- Based on your insistence that the problem must be on Jetty side I did in-depth investigation. Indeed, turned out that Jetty requires a very specific configuration for graceful shutdown to work - specifically a working StatisticHandler. Originally, I did have this handler created but it was not properly invoked / integrated into the handler chain. After fixing this problem (and adding logging of the StatisticHandler stats at the request start/stop and server shutdown start/stop times) I found that all exceptions / errors go away after thorough testing. In the logs I can observe the case of server shutdown invoked in the middle of multiple requests processing and then seeing them through to graceful completion, before server shutdown completion. Here is the reference for the Jetty issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=420142 Just for the record this final test was completed under the following settings in the VirtualHost: SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 SetEnv proxy-initial-not-pooled 1 RequestHeader unset Expect early ... and this balancer setup: <Proxy balancer://mybalancer> ProxySet failonstatus=502,503 maxattempts=1000 BalancerMember http://host1:9999 timeout=3600 retry=0 ping=30 disablereuse=on keepalive=on BalancerMember http://host2:9999 timeout=3600 retry=0 ping=30 disablereuse=on keepalive=on BalancerMember http://host3:9999 timeout=3600 retry=0 ping=30 disablereuse=on keepalive=on </Proxy> I intend to leave these settings "as is" for our production system, unless there is a good reason (and low risk) to restore keep alives or if you might advise change any other changes... I suppose if all requests have large payloads, the keepalives won't be adding much benefit? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
