WCF Client proxy

Hi Shalini,

WCF session is managed by client proxy lifetime so when you close the proxy it sends such information to serever so the remote service could be released.Even if you're not using sessions in your WCF service code, bindings like wsHttpBinding with Windows security will open session automatically (for performance optimization reasons).

If you're not closing proxies correctly, after you made maxConcurrentSessions calls, you'll receive TimeoutException or a significant delay.

Always check for the status of proxy before closing it because closing the proxy safely in 3.5 was itself an issue. I found a code snippet to close the WCF client proxy safely and nochance of leaving the proxy state open.

public static class ClientBaseExtenstion
 {
     /// 
     /// Transitions proxy to closed state via Close() or Abort() 
     /// dependently on current proxy state
     /// 
     public static void CloseProxy(this ClientBase proxy) where T : class
     {
         try
         {
             if (proxy.State != CommunicationState.Closed &&
         proxy.State != CommunicationState.Faulted)
             {
                 proxy.Close(); // may throw exception while closing
             }
             else
             {
                 proxy.Abort();
             }
         }
         catch (CommunicationException)
         {
             proxy.Abort();
             throw;
         }
     }
 }

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Amit Choudhary15y ago
Hi Shalini,

WCF session is managed by client proxy lifetime so when you close the proxy it sends such information to serever so the remote service could be released.Even if you're not using sessions in your WCF service code, bindings like wsHttpBinding with Windows security will open session automatically (for performance optimization reasons).
If you're not closing proxies correctly, after you made maxConcurrentSessions calls, you'll receive TimeoutException or a significant delay.
Always check for the status of proxy before closing it because closing the proxy safely in 3.5 was itself an issue. I found a code snippet to close the WCF client proxy safely and nochance of leaving the proxy state open.

public static class ClientBaseExtenstion
{
    ///

    /// Transitions proxy to closed state via Close() or Abort()
    /// dependently on current proxy state
    ///

    public static void CloseProxy(this ClientBase proxy) where T : class
    {
        try
        {
            if (proxy.State != CommunicationState.Closed &&
        proxy.State != CommunicationState.Faulted)
            {
                proxy.Close(); // may throw exception while closing
            }
            else
            {
                proxy.Abort();
            }
        }
        catch (CommunicationException)
        {
            proxy.Abort();
            throw;
        }
    }
}
0