| Summary: | on major load on the server, poll() hangs | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | tal.yalon |
| Component: | mpm_worker | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED LATER | ||
| Severity: | major | CC: | tal.yalon |
| Priority: | P2 | Keywords: | MassUpdate |
| Version: | 2.2.16 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
tal.yalon
2011-03-09 09:34:35 UTC
We have to see the parameters passed to poll() (perhaps from strace, perhaps from a backtrace on a debug build, perhaps from somebody understanding the assembly code with the same build you got the backtraces from). The timeout is hard-coded to 2 seconds, so it isn't supposed to block longer than that. A FIN has already been sent on the connection, so poll() could wake up on socket activity before "too long." If server-status is enabled, a thread with this backtrace should show up as "C" (closing). (In reply to comment #1) > We have to see the parameters passed to poll() (perhaps from strace, perhaps > from a backtrace on a debug build, perhaps from somebody understanding the > assembly code with the same build you got the backtraces from). > > The timeout is hard-coded to 2 seconds, so it isn't supposed to block longer > than that. If the remote partner (in this case the client) does not close the socket we can return to the poll call over and over again for the next 30 seconds. We only stay in a single poll call for at max 2 seconds, but may have up to 15 calls to poll. thanks, Ruediger we need to distinguish between blocking in a single poll() call for a long time vs. repeatedly calling poll(); strace would make that clear; gdb could make that clear as well if used properly 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. |