More info. See article below.
So, what I think is:
My dev workstation is an XP Pro machine. I'm assuming that it has the
10 user limit ( which is great from a marketing perspective that M$ can
limit people from running an XP server, but sucks eggs as far as me, the
developer, wanting to benchtest a production web service locally!) The
article says that even if I disable the keep-lives, I still am up
against the 10 person limit....in fact, by disabling the keep alives, my
web service calls probably happen so fast they overwhelm the II5 server
on XP and thus the lock up decribed below ( possibly ).
So, my guess is the disabling of the Keep-Alives on my production web
server ( which is running 2k server ) may have the intended effect of
lessening the number of calls to the web service that return the 403.9
Error Message: HTTP 403.9 - Access Forbidden: Too many users are connected
If more than ten connections are needed, use the version of IIS 5.0 that
is included in Windows 2000 Server.
If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on Microsoft
Windows XP Professional, disable HTTP keep-alives in the properties of
the Web site. When you do this, a limit of 10 concurrent connections
still exists, but IIS does not maintain connections for inactive users.
John Bailo wrote: