WCF ServiceHost.Close() Delay

c# wcf duplex
Jasper Chan picture Jasper Chan · Jun 22, 2009 · Viewed 9.7k times · Source

I have a simple WCF duplex TCP service that I am trying to stop programmatically. If I don't have any connected users, ServiceHost.Close() is very quick but if I even have one connected user, I find the Close() function to take quite a bit of time, sometimes >30seconds. Is this usual behavior?

On the other hand, Abort() is almost instantaneous and I am tempted to use that instead.

Answer

Scott Weinstein picture Scott Weinstein · Jun 22, 2009

It may be. The docs state that

The Close method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages.

There is an overload to Close() which takes a TimeSpan (and throws if the timespan is exceeded)

Abort() looks like the best way to stop a WCF host without delay.

Related questions

Could not find a base address that matches scheme net.tcp

I have moved my file transfer service from basicHttpBinding to netTcpBinding as I am trying to set up a duplex mode channel. I have also started my net.tcp port sharing service. I am currently in dev and am self …

Read More
Detecting Client Death in WCF Duplex Contracts

I'm trying to build a SOA where clients can perform long running queries on the server and the server responds using a callback. I'd like to be able to detect if the client disconnects (through user initiated shutdown, unhandled exception …

Read More
How to handle WCF exceptions (consolidated list with code)

I'm attempting to extend this answer on SO to make a WCF client retry on transient network failures and handle other situations that require a retry such as authentication expiration. Question: What are the WCF exceptions that need to be …

Read More