Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3F248A94.40403@wstoddard.com>
Date: Sun, 27 Jul 2003 22:29:40 -0400
From: Bill Stoddard <bill@wstoddard.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Message: winnt_accept: Asynchronous AcceptEx failed.
References: <423019046EC9F647AF13F367FB01C15801D7813F@ftlpexch501>
In-Reply-To: <423019046EC9F647AF13F367FB01C15801D7813F@ftlpexch501>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Alex Bereznyi wrote:

> Hi,
> 
>  
> 
> We see a lot of WARNING messages in Windows Event Log:
> 
> * *
> 
> *winnt_accept**: Asynchronous AcceptEx failed. *
> 
>  
> 
> The actual error is always 995: ERROR_OPERATION_ABORTED - The I/O 
> operation has been aborted because of either a thread exit or an 
> application request.
> 
>  
> 
> It's coming from *server\mpm\winnt\child.c*
> 
> The call:
> 
>  
> 
> GetOverlappedResult((HANDLE)context->accept_socket,
> 
>                                              &context->Overlapped,
> 
>                                              &BytesRead, FALSE)
> 
>  
> 
> GetLastError()  is not called there, instead:
> 
>  
> 
>                         closesocket(context->accept_socket);
> 
>                         context->accept_socket = INVALID_SOCKET;
> 
>  
> 
> It all seems like normal condition to me - why log WARNING ? Is it OK to 
> turn it off?
> 

I'll turn this into an info message. I agree it should not be a warning.

Bill