Article ID: 2536618 - View products that this article applies to.
Consider the following scenario:
Log Name: System
Source: SMSvcHost 126.96.36.199
Event ID: 8
Task Category: Sharing Service
User: LOCAL SERVICE
Description: An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
System.TimeoutException: This request operation sent to did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.Note You must restart IIS to recover the WCF service from this issue.
This issue occurs because the Smsvchost.exe process times out after one minute when it tries to transfer an incoming connection request to the W3wp.exe worker process. Additionally, this time-out is non-configurable.
When the CPU has a heavy workload, or when many concurrent connection requests are incoming, the Smsvchost.exe process cannot transfer the incoming connection to the W3wp.exe worker process within one minute. Therefore, the Smsvchost.exe process times out and eventually stops responding. When this issue occurs, the Smsvchost.exe process cannot route later requests to the W3wp.exe worker process until IIS is restarted.
To resolve this issue, apply hotfix 2504602 that is described in Microsoft Knowledge Base (KB) article.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2504602/ )A hotfix rollup package is available for WCF in the .NET Framework 3.0 SP2 and in the .NET Framework 4
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.