Armin Abfalterer

I did some tests with HTTP/2 and could see that the "connection counter" didn't go back to zero when there were no more connections on the proxy. However, I still couldn't reproduce that the counter is constantly growing, even with HTTP/2. Anyway, thanks for the improvements... I'll give 11.49 a try.

Pascal, yes - the proxy uses mod_http2.

no, there were no unexpected child exits yes, the system was up about 30 days and there were some graceful restarts in between (due to configuration changes) MaxConnectionsPerChild is set to 1000000 btw, I did some testing with graceful restarts and forced child exits but couldn't reproduce the misbehavior. I think massive load plays an important role here...

ok, with that patch the counter might not be increased anymore. but the problem that it isn't counted down might still exist, or how do you see it?

no, there were no unexpected child exits yes, the system was up about 30 days and there were some graceful restarts in between (due to configuration changes) MaxConnectionsPerChild is set to 1000000

Hi Pascal, thanks for your reply! Ok, but on this system the "concurrent connections" counter didn't go down any more, so that all further connections were blocked. As you can see in the log excerpt the time span was over 10 hours. The only place in the code that decrements the counter is the one in qos_cleanup_conn () if((m_generation != u->qos_cc->generation_locked) && u->qos_cc->connections > 0) { u->qos_cc->connections--; } I could imagine something went wrong with the generation counter m_generation....

Hi We have a problem with a httpd proxy-server (httpd 2.4.25 with mod_qos 11.39) causing under heavy load to block all incoming connections as soon as QS_ClientPrefer limit is reached. It seems the counter of "concurrent connections" is not decremented correctly. When the first mod_qos(066) event was triggered the number of concurrent connections was 959. From this point on, the counter was getting only higher (up to 13431) though MaxRequestWorkers is 1024. [Tue Jan 23 13:42:02 2018] [error] mod_qos(066):...