| Summary: | KeepAliveTimout prevents child process from exiting cleanly with winnt_mpm | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | NG <neel.goyal> |
| Component: | mpm_winnt | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | steven.BUSH |
| Priority: | P2 | Keywords: | MassUpdate |
| Version: | 2.2.11 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
|
Description
NG
2009-04-03 10:16:56 UTC
I just ran into this as well. We have a custom module that has a hook into the shutdown via apr_pool_cleanup_register(). If the KeepAliveTimeout is set to anything greater than 30 seconds (the hardcoded "death to all children time" as mentioned in NG's comment), our cleanup is never called and various resources fail to get cleaned up. We're working around this through other means, but it seems that when the server is shutting down, the child thread that is in a keep-alive state waiting for a further request should close its socket and exit rather than waiting for the end of the keep-alive timeout. For one thing, any further requests by the client will be ignored, so there doesn't appear to be a benefit to staying open. You can see the effect quite easily with a simple configuration: 1. httpd.conf with KeepAliveTimeout set to something > 30 seconds (say 60) 2. a Module with a cleanup hooked into apr_pool_cleanup_register() 3. start server 4. make a single keep-alive request to server-status (or any other resource) 5. shut down server --> you will find that the server takes ~30 seconds to shutdown and the cleanup is never called Repeat, but eliminate the connection in step 4: --> process shuts down in ~2-5 seconds and clean up is called Repeat, but this time reduce the KeepAliveTimeout to < 10 seconds (say 10) --> process shuts down in ~5-15 seconds and clean up is called 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. |