HTTP Server errors after upgrade to WebSphere 6.0

All,

We recently upgraded to WebSphere 6.0. Now, some of our users are reporting that they are kicked out of EOne after 5 minutes. I have verified and re-verified that the timeouts are set correctly for 30 minutes in the httpd.cof, jas.ini, and WebSphere. I have found that there are connection errors in the http server logs.. Does anyone have any idea what could causes this. My hunch is that there is some sort of "keep-alive" that is failing between the client and http server, but that is just a hunch. Any ideas?

[Fri Jul 27 14:47:24 2007] [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:47:24 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:47:24 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:47:24 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:47:24 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:48:05 2007] [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:48:05 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:54:42 2007] [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 14:58:15 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 15:08:12 2007] [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 15:08:13 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 15:09:08 2007] [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed.
[Fri Jul 27 15:09:08 2007] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.


Thanks...

While researching this issue, I found the following:

AcceptEx() is a Microsoft WinSock v2 API that provides some performance improvements over the use of the BSD style accept() API in certain circumstances. Some popular Windows products, typically virus scanning or virtual private network packages, have bugs that interfere with the proper operation of AcceptEx(). If you encounter an error condition like:


AcceptEx() can be disabled in the httpd.conf file on Http Server V6, you just need to uncomment the directive, it's in there already....

#Use Win32DisableAcceptEx to downgrade to use winsock 1.1 network APIs.
# Note: You can use Win32DisableAcceptEx only if mod_afpa_cache.so is disabled.
# Win32DisableAcceptEx
</IfModule>