I have a WCF application where serveral clients connect to a server.
I'm totally aware of the fact that I should always call the
'Proxy.Close()' method everytime the client quits to free some IIS
resources (assuming my service is housed in IIS) allowing other
clients to connect. I'm also aware of the fact that the server can
only handle 'maxConcurrentS essions' concurrent clients at the same
time (which is set to 10 by default).
My concern is, what if a client got abruptly aborted, thus, the
"Proxy.Clos e()" did not get called? Is there a way the server can free
those resources (from IIS) to be used by other clients? [The problem
appears if 10 clients where aborted thus the server will no more
accept connections since clients did not close the proxy when
quitting]
Thanks
I'm totally aware of the fact that I should always call the
'Proxy.Close()' method everytime the client quits to free some IIS
resources (assuming my service is housed in IIS) allowing other
clients to connect. I'm also aware of the fact that the server can
only handle 'maxConcurrentS essions' concurrent clients at the same
time (which is set to 10 by default).
My concern is, what if a client got abruptly aborted, thus, the
"Proxy.Clos e()" did not get called? Is there a way the server can free
those resources (from IIS) to be used by other clients? [The problem
appears if 10 clients where aborted thus the server will no more
accept connections since clients did not close the proxy when
quitting]
Thanks