If my client app calls web services one at a time, shouldn't the previous socket be closed before the next socket is open? And in this case, I'm only managing to get around 8 web service calls before it starts failing.
8 is not very many. -j --- Ephemeris Lappis <[EMAIL PROTECTED]> wrote: > Are you sure the problem is the http connections ? > I remember, long time ago, a problem with sockets on > windows workstation > systems (NT and 2000) which source was the limited > socket numbers. If i > remember well, unlike server versions, workstation > configurations limit > socket number up to 5000. In a typical case when > both your server and your > client run on the same system, you can quickly > consume all your accepted > numbers. If you want more, you have to change some > key in the registry > (sorry, i don't remember which one). The problem > comes when many connections > are open in a short time. You must also adjust the > time the stack keeps the > socket in close-wait state before the number can be > used again... You can > check it with a netstat or a similar tools. > I hope this can help you. > > > >>> -----Original Message----- > >>> From: John Windberg [mailto:[EMAIL PROTECTED] > >>> Sent: Wednesday, May 18, 2005 3:44 AM > >>> To: [email protected] > >>> Subject: running out of sockets??? > >>> > >>> > >>> I'm writing client code against Autodesk Vault > web > >>> services which are .Net code within an IIS > instance. > >>> After a series of calls I start getting "out of > >>> sockets" or "access denied" errors, which seem > to be > >>> caused because IIS on this XP instance has a > limited > >>> number of available connections. > >>> > >>> I'm only calling one at a time. Why would my > >>> connections not be getting closed? > >
