Thanks for the heads up. The shutdown behaviour is most likely influenced by how many connections are open at that time and http2 connection are kept open longer by clients. Probably we can improve the observed behaviour. There has not been much focus on that part of the protocol handling...
If you could open a ticket and include a server-status response just before and maybe during? Thanks! //Stefan > Am 20.09.2015 um 11:00 schrieb Steffen <[email protected]>: > > > With mod_h2, noticed that shutting down takes quite long time ~30 sec, > > > [Sun Sep 20 10:20:12.724460 2015] [mpm_winnt:notice] [pid 5860:tid 396] > AH00422: Parent: Received shutdown signal -- Shutting down the server. > [Sun Sep 20 10:20:42.726181 2015] [mpm_winnt:notice] [pid 5860:tid 396] > AH00431: Parent: Forcing termination of child process 5988 > > without mod_h2 it takes ~2 sec: > > > [Sun Sep 20 10:31:07.421791 2015] [mpm_winnt:notice] [pid 8244:tid 392] > AH00422: Parent: Received shutdown signal -- Shutting down the server. > [Sun Sep 20 10:31:09.438615 2015] [mpm_winnt:notice] [pid 8796:tid 308] > AH00364: Child: All worker threads have exited. > [Sun Sep 20 10:31:09.454280 2015] [mpm_winnt:notice] [pid 8244:tid 392] > AH00430: Parent: Child process 8796 exited successfully. > > Steffen > > <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
