1

I have faced the problem with the connection limited in WCF. My WCF service was hosted in IIS and my windows form application client connects to WCF. In the Windows_Closed event, I call the client.Close() method to notify the WCF service that "I quit" but in cases of my client crashed, the connection between my client and WCF service still exists for a time, I simulated 10 crashed time then my app did not work anymore.

And the question is, how to release the connection between WCF and crashed client? because the maxConnections of the server is limited and equal to 10 for example.

Thanks you!

Bac Clunky
  • 353
  • 3
  • 6
  • 18

3 Answers3

2

You could use the InactivityTimeout as Brijesh points out if you are using ReliableSession. Otherwise you should leverage the basic WCF timeouts.

See Timeouts WCF Services for a description of how each timeout is implemented.

Timeouts are often an annoyance for developers, but this is precisely the purpose for which they exist.

Community
  • 1
  • 1
Kirk Broadhurst
  • 27,836
  • 16
  • 104
  • 169
1

you can make use of Inactivity Timeout . Here server will automatically close connection if it doesnot recieve message during specified time frame.

Brijesh Mishra
  • 2,738
  • 1
  • 21
  • 36
-1

You can make use of using code block in your client:

using(ClientClass client = new ClientClass){
//Call service here
}

This isn't really reliable so you may want to go for try-catch-finally instead. Make sure that client.Abort is called in each of the catch blocks.

danish
  • 5,550
  • 2
  • 25
  • 28
  • finally block will not execute for certain type of crash, like powefailure, out of memory, stack overflow, ExecutingEngineException – Brijesh Mishra Jul 20 '12 at 05:58