Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 78064 invoked by uid 500); 30 Jul 2003 19:56:06 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 75959 invoked from network); 30 Jul 2003 19:55:27 -0000 Message-ID: <3F2822A4.6080507@wstoddard.com> Date: Wed, 30 Jul 2003 15:55:16 -0400 From: Bill Stoddard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Message: winnt_accept: Asynchronous AcceptEx failed. References: <69EB8DF424C8FE409AF8FFAF1B19787AE1968C@ftlpexch502> In-Reply-To: <69EB8DF424C8FE409AF8FFAF1B19787AE1968C@ftlpexch502> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > 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) > > > > I've looked at this a bit and I amend my last answer to this thread. I can see no good reason (and some very bad reasons) for GetOverlappedResult failing here with this error. My guess... you have a package that installed a network service provider filter and that filter is somehow doing a close on the event handle in the overlapped structure. Or perhaps another thread in the server is closing the handle. Do you have any other interesting modules loaded into the server?. What level of Apache 2 are you using? Can you tell me anything else about the circumstances when you see these messages? Can you associate any changes in your environment or configuration with the appearance of these message in your log files? Bill