WCF Windows Service TimeOut

Question

I have a client application developed in .net seding a request to wcf service and supposed to send reponse .if execution time with in 1 minute,there is no error,if it exceeds 1 minute the error is

Inner exception: This request operation sent to net.tcp://localhost:18001/PitToPort/2008/01/30/StockpileService/tcp 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

How to increase the time out and how? What is the best solution?

Answer 1

Be careful, this error message is a boilerplate string WCF sends when it doesn't have a clue what happened. It really means "mmh something went wrong in the chain but I'm not really sure what, so, here's some trivia about the configuration, do what you want with it".

MOST OF THE TIME when you get this message it has nothing to do with actual timeouts. It can be quotas (number of objects in the graph, overall size, array length) or something that went wrong server-side, between the time your service method returned a result and the actual bytes were sent over the wire. So, you should check your configuration settings (and not the timeout, except if you had to actually wait for one minute to get the error. If you got the error straight away, it has nothing to do with timeouts whatsoever).

This useless message is on top of my list of WCF annoyances.

Answer 2

The timeout is called "sendTimeout" and you can configure it on your binding section in your config file, or in code - your choice.

config:

  <system.serviceModel>
    <bindings>
      <netTcpBinding>
        <binding sendTimeout="00:03:00" />
      </netTcpBinding>
    </bindings>

This will set the timeout to 3 minutes.

Marc

Answer 3

I have add the following code to the Service app code

system.transactions  
    defaultSettings timeout="00:30:00" 

with this code the service will wait 30 minutes to get process done in database server and increase the

maxBufferSize="2147483647"  
maxReceivedMessageSize="2147483647"  
maxBufferPoolSize="2147483647" 

in client binding attributes, then it works fine.

Problem :Service is sending response but the client buffersize was less previously,I increased to maximum buffer size.

Answer 4

I experienced this same error. Specifically, the exception that I received was:

System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:09:59.9940000'.

System.IO.IOException: The write operation failed, see inner exception.

System.ServiceModel.CommunicationException: The socket connection was aborted.

This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue.

Local socket timeout was '00:09:59.9940000'.

System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

The cause of my problem was due to the size of the message that was being sent from my WCF Client to the WCF Host. Apparently, the size of the message was too large.

To fix the problem, I changed the hosts Web.Config maxReceivedMessageSize attribute from 2097152 to 8000000 and the error no longer persisted.

Here's the Web.Config's attribute I'm referring to:

<netTcpBinding>
<binding name="NetTCPBinding" maxReceivedMessageSize="8000000">
....
</binding>
</netTcpBinding>

The 8M message size that I chose was based on how large I "think" the message size is. I don't know of a way to explicitly determine the size of the actual WCF message that gets passed from the client to the host.

Answer 5

Check this out, for similar type of Error u have to set OperationTine out property http://www.codeproject.com/KB/WCF/WCF_Operation_Timeout_.aspx

Answer 6

If you know why the server is taking more than a minute to respond to the client, then you should extend the OperationTimeout of the channel (as it says in the error message).

Check out this, including a code sample at the end: http://final-proj.blogspot.com/2009/09/wcf-timeouts.html

Good luck.

Answer 7

Here is a far simpler solution... just set the property directly on the current ClientBase. In other words, first add a service reference, initalize it, then set the property "InnerChannel.OperationTimeout"

NetUtilsWCF.SMTPDiagClient sClient = new NetUtilsWCF.SMTPDiagClient();

sClient.InnerChannel.OperationTimeout = new TimeSpan(0, 5, 0);

Answer 8

I got the same exception when using callback.It works in local test(the client and service program are running in the same machine) but not work in user environment(the service program runs in winserver 2008). The server code has executed in according to the log.I think it's because of environment or authority problem but have no idea how to handle.

Answer 9

If you are facing the problem after correcting the config file then you may need to check this attribute. "OperationContract(IsOneWay:=True)". If you miss IsOneWay:=True attribute it may cause this problem.