blocks|key|410668|text|超时时间称为"sendTimeout“，您可以在配置文件的绑定节上配置它，也可以在代码中配置它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410669|配置：|410670|++<system.serviceModel>
++++<bindings>
++++++<netTcpBinding>
++++++++<binding+sendTimeout="00:03:00"+/>
++++++</netTcpBinding>
++++</bindings>|code-block|syntax|javascript|410671|这会将超时设置为3分钟。|410672|Marc|410673|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

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

config:

<pre><code> &lt;system.serviceModel&gt;
 &lt;bindings&gt;
 &lt;netTcpBinding&gt;
 &lt;binding sendTimeout="00:03:00" /&gt;
 &lt;/netTcpBinding&gt;
 &lt;/bindings&gt;
</code></pre>

This will set the timeout to 3 minutes.

Marc

blocks|key|3254636|text|我已经将以下代码添加到服务应用程序代码中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3254637|system.transactions++
++++defaultSettings+timeout="00:30:00"+|code-block|syntax|javascript|3254638|使用此代码，服务将等待30分钟以在数据库服务器中完成处理，并增加|3254639|maxBufferSize="2147483647"++
maxReceivedMessageSize="2147483647"++
maxBufferPoolSize="2147483647"+|3254640|在客户端绑定属性中，它工作得很好。|3254641|问题:服务正在发送响应，但客户端缓冲区大小之前较小，我增加到最大缓冲区大小。|3254642|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I have add the following code to the Service app code

<pre><code>system.transactions 
 defaultSettings timeout="00:30:00" 
</code></pre>

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

<pre><code>maxBufferSize="2147483647" 
maxReceivedMessageSize="2147483647" 
maxBufferPoolSize="2147483647" 
</code></pre>

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.

blocks|key|410675|text|请注意，此错误消息是WCF在不知道发生了什么情况时发送的样板字符串。这实际上意味着“嗯，链中出了点问题，但我真的不确定是什么，所以，这里有一些关于配置的琐事，可以随心所欲地处理它”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410676|大多数情况下，当您收到此消息时，它与实际超时无关。它可以是配额(图中的对象数量、总大小、数组长度)，也可以是在您的服务方法返回结果和通过网络发送实际字节之间的服务器端出了问题。因此，您应该检查您的配置设置(而不是超时，除非您必须真正等待一分钟才能得到错误。如果你马上就得到了错误，那么它与超时无关)。|410677|这条无用的消息在我的WCF烦心事清单的首位。|410678|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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.

blocks|key|416355|text|如果您知道为什么服务器需要一分钟以上的时间来响应客户端，那么您应该扩展通道的OperationTimeout+(如错误消息中所述)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|416356|查看以下内容，在末尾包含一个代码示例：http://final-proj.blogspot.com/2009/09/wcf-timeouts.html|offset|length|416357|祝好运。|416358|entityMap|0|LINK|mutability|MUTABLE|url|http://final-proj.blogspot.com/2009/09/wcf-timeouts.html^0|0|J|1K|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

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:
<a href="http://final-proj.blogspot.com/2009/09/wcf-timeouts.html" rel="nofollow noreferrer">http://final-proj.blogspot.com/2009/09/wcf-timeouts.html</a>

Good luck.

blocks|key|410680|text|这里有一个简单得多的解决方案...只需在当前ClientBase上直接设置属性即可。换句话说，首先添加一个服务引用，初始化它，然后设置属性"InnerChannel.OperationTimeout“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410681|新的sClient+=+NetUtilsWCF.SMTPDiagClient+NetUtilsWCF.SMTPDiagClient()；|410682|sClient.InnerChannel.OperationTimeout+=新的TimeSpan(0，5，0)；|410683|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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);

blocks|key|3467706|text|我也经历过同样的错误。具体地说，我收到的异常是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3467707|3467708|+System.ServiceModel.CommunicationException:套接字连接已中止。这可能是由于处理消息时出错、远程主机超过了接收超时时间或基础网络资源问题造成的。本地套接字超时时间为'00:09:59.9940000‘。|blockquote|3467709|3467710|System.IO.IOException:写入操作失败，请参见内部异常。|3467711|System.ServiceModel.CommunicationException:套接字连接已中止。|3467712|这可能是由于处理消息时出错、远程主机超过了接收超时时间或基础网络资源问题造成的。|3467713|本地套接字超时时间为'00:09:59.9940000‘。|3467714|System.Net.Sockets.SocketException:现有连接已被远程主机强制关闭|3467715|3467716|问题的原因是由于从我的WCF客户端发送到WCF主机的消息的大小。显然，消息太大了。|3467717|为了解决这个问题，我将hosts+Web.Config+maxReceivedMessageSize属性从2097152更改为8000000，错误不再存在。|offset|length|style|CODE|3467718|下面是我引用的Web.Config属性：|3467719|<netTcpBinding>
<binding+name="NetTCPBinding"+maxReceivedMessageSize="8000000">
....
</binding>
</netTcpBinding>|code-block|syntax|javascript|3467720|我选择的8M消息大小是基于我“认为”的消息大小。我不知道有什么方法可以显式地确定从客户端传递到主机的实际WCF消息的大小。|3467721|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|S|M|1H|7|1R|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1C|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1F|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1K|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1L|8|@$V|1M|W|1N|X|Y]|$V|1O|W|1P|X|Y]|$V|1Q|W|1R|X|Y]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1S|8|@]|9|@]|A|$]]|$1|11|3|12|5|13|7|1T|8|@]|9|@]|A|$14|15]]|$1|16|3|17|5|6|7|1U|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|19|$]]

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

<blockquote>
 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
</blockquote>

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 <code>maxReceivedMessageSize</code> attribute from <code>2097152</code> to <code>8000000</code> and the error no longer persisted.

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

<pre><code>&lt;netTcpBinding&gt;
&lt;binding name="NetTCPBinding" maxReceivedMessageSize="8000000"&gt;
....
&lt;/binding&gt;
&lt;/netTcpBinding&gt;
</code></pre>

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.

blocks|key|3467758|text|检查一下，对于类似类型的错误，您必须在属性http://www.codeproject.com/KB/WCF/WCF_Operation_Timeout_.aspx中设置OperationTine|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3467759|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeproject.com/KB/WCF/WCF_Operation_Timeout_.aspx^0|L|1P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Check this out, for similar type of Error u have to set OperationTine out property
<a href="http://www.codeproject.com/KB/WCF/WCF_Operation_Timeout_.aspx" rel="nofollow">http://www.codeproject.com/KB/WCF/WCF_Operation_Timeout_.aspx</a>

blocks|key|3467782|text|如果您在更正配置文件后遇到此问题，则可能需要检查此属性。"OperationContract(IsOneWay:=True)".如果您缺少IsOneWay:=True属性，则可能会导致此问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3467783|entityMap^0|S|10|1X|E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

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

blocks|key|3254721|text|当我在本地测试中使用callback.It+works+(客户端和服务程序在同一台机器上运行)而不是在用户环境中工作(服务程序在Winserver2008中运行)时，我得到了相同的异常。服务器代码已经根据日志执行了，我想可能是环境或权限问题，但不知道该如何处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3254722|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

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

<blockquote>
 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
</blockquote>

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

WCF Windows Service TimeOut

数据库

服务器

我有一个在.net中开发的客户端应用程序，需要在1分钟内发送响应.if执行时间，如果超过1分钟，错误是net.tcp://localhost:18001/PitToPort/2008/01/30/StockpileService/tcp内部异常:发送到的此请求操作在配置的超时(00:01:00)内未收到回复。分配给此操...

问WCF Windows服务TimeOut
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF Windows服务TimeOutEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF Windows服务TimeOut
EN