WCF Service – Configuring Timeouts for Binding

• Address means “Where to find the service?”
• Binding means “How to communicate with service?”
• Contract defines “What to communicate?

As WCF Service Binding defines all about how to communicate. It plays an important role in managing performance and security for the service. So,understanding timeouts configuration values on binding will definitely have impact on performance, usability as well as security.Few days back, one of my colleague was facing an issue of inactivity timeout on aWCF service. We spend sometime looking into configuration and find out that “ReceiveTimeout” value on bindingwas set to a very short value.So, In order to resolve the issue, we just increase this timeout value to something bigger and reasonable as shown below. For the purpose of sharing, I am writing thisWCF Service Tutorial.<bindings>
        <netTcpBinding>
            <binding receiveTimeout=”00:30:00″………>
            </binding>
        </netTcpBinding>
    </bindings>

“ReceiveTimeout” value on binding actually defines how long a session will remain idle before timing out.

Various timeout values on binding are listed below and we can find its detail here:

1. OpenTimeout
2. CloseTimeout
3. SendTimeout
4. ReceiveTimeout