Hi Everyone,

I have a windows service which consumes a web service on a separate machine
in our network. I modified my machine.config to allow my service application
to make 200 connections to the server at once, and I spool up to 200 threads
at once to make calls to the server. All of this works great and as expected.

However I have noticed that by default the underlying connections tend to
stay open for about 90 seconds after my web service calls terminate. So if I
use a tool like TCPView I can see that I still have hundreds of connections
that remain open even after explicitly calling the .Dispose() method of my
proxy objects.

Is there a way that I can force those connections to close from my Service?
Or is that controlled by the server?

Thanks a Million.

John Rossitter