On Mon, Sep 16, 2013 at 11:38 AM, Gregg Smith <[email protected]> wrote: > On 9/16/2013 12:13 AM, Ivan Zhakov wrote: >> >> On Mon, Sep 16, 2013 at 12:49 AM, Steffen<[email protected]> wrote: >>> >>> Current behavior with windows httpd 2.46 is that with AcceptFilter that >>> the >>> sever always starts with good traffic. Most of us dealing then with >>> periodic traffic hangs, slow traffic and/or log entries like Asynchronous >>> AcceptEx failed. We advise in the info to set with issues to >>> AcceptFilter >>> http none and AcceptFilter https none. >>> >>> >> Did you have problem with "AcceptFilter connect" or "AcceptFilter >> data" ? What error code is logged with AcceptEx failed error? > > It's a very common error, more often than not. AcceptFilter data or connect > matters not, none is the only way to get rid of it! > > OS 64)The specified network name is no longer available. : AH00341: > winnt_accept: Asynchronous AcceptEx failed. > Socket reuse seems to be problem. Documentation says that socket must be not bound or connected. I.e. DisconnectEx() function with TF_RESUE_SOCKET flag should be called to reuse socket in AcceptEx()/ConnectEx [1] [[[ TF_REUSE_SOCKET
Prepares the socket handle to be reused. When the DisconnectEx request completes, the socket handle can be passed to the AcceptEx or ConnectEx function. Note The socket level disconnect is subject to the behavior of the underlying transport. For example, a TCP socket may be subject to the TCP TIME_WAIT state, causing the DisconnectEx call to be delayed. ]]] [1] http://msdn.microsoft.com/en-us/library/windows/desktop/ms737757 -- Ivan Zhakov
