Detect socket disconnect in WCF

15,722

Any WCF channel implements ICommunicationObject , which provides events for the channel lifetime.

You should listen to the Faulted event

The sessionId can be accessed as always from the OperationContext.Current property.

When your client open the channel (on the first operation), register to the adequate events:

OperationContext.Current.Channel.Faulted += new EventHandler(Channel_Faulted);
OperationContext.Current.Channel.Closed += new EventHandler(Channel_Faulted);

and:

 void Channel_Faulted(object sender, EventArgs e)
 {
     Logout((IContextChannel)sender);
 }

 protected void Logout(IContextChannel channel)
 {
        string sessionId = null;

        if (channel != null)
        {
            sessionId = channel.SessionId;
        }
      [...]
 }
Share:
15,722
Soonts
Author by

Soonts

Potentially interested in full-time position or contracts. Open to working remotely, have been doing that since 2012. Areas of interest are videogames, embedded, CAD/CAM, robotics, performance optimization, GPGPU. You can reach me at [email protected]

Updated on June 22, 2022

Comments

  • Soonts
    Soonts almost 2 years

    We're building a WCF server (.NET 4.0). It will only use net.tcp transport.

    When a client closes the TCP connection, the server gets unhandled CommunicationException, and terminates.

    Q1. How do I handle the CommunicationException so the server does not terminate and continues serving other clients?

    Q2. In the handler, how do I get SessionId of the session that was aborted? I need this to do clean up some session-specific data.

    Thanks in advance!

    P.S. The connection is over the Internet, so the socket may be closed anytime, regardless on whether the client disconnects gracefully, or not.