https://issues.apache.org/bugzilla/show_bug.cgi?id=57520
--- Comment #5 from dk <[email protected]> --- "Connection refused" messages in the error log are expected since after Jetty JVM exits it won't be listening on ports while it is restarting. While Jetty is still shutting down and waiting for existing requests to finish it responds with 503. In httpd I have failonstatus set to handle that. Could you recommend the specific pcap or tcpdump settings to capture the connection info you need? I believe capturing the entire traffic payload would be way too heavy and I am not sure if/how I can even post huge logs into this issue tracker. I have 3 boxes in the cluster/balancer with Jetty/httpd on each and one client box issuing round robin stress test requests - 30 threads at the time. Could you specify exactly what you want me to do? As far as ttl/keepalives - yes this reported behavior is seen under "proxy-nokeepalive" too. TTL is the only setting you mentioned that I have not tried, but I presume it is ignored under nokeepalive regime? Perhaps you could suggest a couple mod_proxy configurations for me to test with the traffic recorder on? I should note, it might take a few runs (generating pretty big logs) since the error behavior is quite flaky and occurs sporadically - depending on how the Jetty restart is exactly timed. -- 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]
