context->accept_socket. This FD will be closed a second time, often
shortly after a worker picks it up in this same FD being reused. The
first recv fails with WSAENOTSOCK since the same FD was closed in the
listener thread while the worker was pulling it off the queue
(The second close is of the underlying FD/socket, not a shared
apr_socket_t, so it's not short-circuited)
This patch makes it a bit more 2.2.x-ish and solves my problem -- the
context->accept_socket gets zapped at the bottom of the loop if
!disconnected.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@
1523387 13f79535-47bb-0310-9956-
ffa450edef68
-*- coding: utf-8 -*-
Changes with Apache 2.5.0
+ *) WinNT MPM: If ap_run_pre_connection() fails or sets c->aborted, don't
+ save the socket for reuse by the next worker as if it were an
+ APR_SO_DISCONNECTED socket. Restores 2.2 behavior. [Eric Covener]
+
*) mod_auth_digest: Be more specific when the realm mismatches because the
realm has not been specified. [Graham Leggett]
if (!c->aborted) {
ap_run_process_connection(c);
+ }
- apr_socket_opt_get(context->sock, APR_SO_DISCONNECTED,
- &disconnected);
+ apr_socket_opt_get(context->sock, APR_SO_DISCONNECTED, &disconnected);
- if (!disconnected) {
- context->accept_socket = INVALID_SOCKET;
+ if (!disconnected) {
+ context->accept_socket = INVALID_SOCKET;
+ if (!c->aborted) {
ap_lingering_close(c);
}
}