| Author |
[warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asyn
|
|
| Jorge Jarpa 2005-01-26, 6:04 pm |
| I have IBM HTTP Server 2.0.47 running on Windows 2000 Server.
I am getting this errors in the HTTP Server's log:
[warn] (OS 64)The specified network name is no longer available. :
winnt_accept: Asynchronous AcceptEx failed.
[warn] (OS 121)The semaphore timeout period has expired. : winnt_accept:
Asynchronous AcceptEx failed.
IBM Says on
http://www-1.ibm.com/support/docvie...dc=DA420&dc=DA5
00&dc=DA410&dc=DB540&dc=DB510& q1=winnt_accept%3a+Asynchronous+AcceptEx
+failed&uid=swg1PQ84990&loc=en_US&cs=utf-8&lang=en
That is a Bug detected:
PQ84990: Periodic performance slowdown problem with AcceptEx.
And it is fixed adding the directive " Win32DisableAcceptEx " in the
httpd.conf file
But When I do that, IBM HTTP Server Service donīt start !
What I am doing wrong ?
Regards,
Jorge Jarpa
| |
| ddkilzer 2005-03-08, 3:56 pm |
| The Win32DisableAcceptEx directive was introduced in Apache v2.0.49. It will look like a bad directive to any version less than v2.0.49.
See the
Win32DisableAcceptEx documentation for details.
Dave
quote:
Originally posted by Jorge Jarpa
I have IBM HTTP Server 2.0.47 running on Windows 2000 Server.
[...]
And it is fixed adding the directive " Win32DisableAcceptEx " in the
httpd.conf file
But When I do that, IBM HTTP Server Service donīt start !
What I am doing wrong ?
Regards,
Jorge Jarpa
| |
| ddkilzer 2005-03-09, 2:53 pm |
| See also the Jan-Mar 2005 posts on Apache Bug 21425.
Dave
quote:
Originally posted by ddkilzer
The Win32DisableAcceptEx directive was introduced in Apache v2.0.49. It will look like a bad directive to any version less than v2.0.49.
See the
Win32DisableAcceptEx documentation for details.
Dave
|
|
|
|