编辑
After looking at this for a while, I thought it might be a configuration issue on my development box. However, after doing a clean download of the source code to a different development machine, I'm still getting this issue.
我有一个异步调用 WCF 服务的 Silverlight 客户端。间歇性地，我会得到一个通用的
NotFound异常(exception)。异常(众所周知缺乏细节)在我调用的几乎所有服务上都会间歇性地发生。事情就是这样。通过明智地设置断点，我已经能够确定服务端正在正常执行。正在检索和返回数据。问题似乎更多地出在客户端。
这就是问题所在......如果我让服务执行超过 10 秒，我可以始终如一地发生异常。当我这样做时，它永远不会回到我完成的回调。相反，我在服务的客户端 Reference.cs 中得到了异常:
public System.Collections.ObjectModel.ObservableCollection<Project.Ui.SilverLight.ServiceName.ModelName> EndGetService(System.IAsyncResult result) {
object[] _args = new object[0];
System.Collections.ObjectModel.ObservableCollection<roject.Ui.SilverLight.ServiceName.ModelName> _result = ((System.Collections.ObjectModel.ObservableCollection<roject.Ui.SilverLight.ServiceName.ModelName>)(base.EndInvoke("GetService", _args, result)));
return _result;
}
我得到的异常(exception)是(不是很有帮助):
System.ServiceModel.CommunicationException was unhandled by user code
Message=The remote server returned an error: NotFound.
StackTrace:
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
at Project.Ui.SilverLight.Service.ServicesClient.ServicesClientChannel.EndGetxxxxx(IAsyncResult result)
at Project.Ui.SilverLight.Service.ServicesClient.Project.Ui.SilverLight.Service.IServices.EndGetxxxx(IAsyncResult result)
at Project.Ui.SilverLight.Service.ServicesClient.OnEndGet(IAsyncResult result)
at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)
InnerException: System.Net.WebException
Message=The remote server returned an error: NotFound.
StackTrace:
at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
InnerException: System.Net.WebException
Message=The remote server returned an error: NotFound.
StackTrace:
at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClass5.<EndGetResponse>b__4(Object sendState)
at System.Net.Browser.AsyncHelper.<>c__DisplayClass2.<BeginOnUI>b__0(Object sendState)
InnerException:
绑定(bind)信息(名称已更改，但它们与正在执行的服务匹配)
<binding name="Project.WebUI.Services.xxxxxServices.customBinding0" closeTimeout="00:01:00"
openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00">
<binaryMessageEncoding/>
<httpTransport />
</binding>
...
<service name="Project.WebUI.Services.xxxxxServices">
<endpoint address="" binding="customBinding" bindingConfiguration="Project.WebUI.Services.xxxxxServices.customBinding0"
contract="Project.WebUI.Services.xxxxxServices" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
</service>
我相信我已经检查了相关的超时。 channel
operationTimeout设置为至少一分钟，ReceiveTimeout 和 OpenTimeout 也是如此。 Silverlight 异步 WCF 调用是否有一些神秘之处需要设置为超过十秒？
最佳答案
未找到您的原因不是由于超时。我花了一周的时间试图弄清楚这一点。
我引用了silverlight，但这不是silverlight 特有的问题。
由于错误代码的产生方式，存在未找到的故障。您需要拦截任何故障并更改错误代码 - 这将导致错误被正确报告并且由于安全原因而不会被过滤掉。
如果您考虑一下，找不到服务器，因为调用是异步的，并且由于代码中的异常而死了。
我在我的 wcf 服务中使用这个类来插入 - 我是通过 web.config 执行此操作的，但是不难更改它，以便它在服务本身上具有类级别属性。
你可能想去掉所有的契约(Contract)内容。它正在我正在从事的项目中使用，但与此问题没有任何关系。
[AttributeUsage(AttributeTargets.Class)]
public class FaultBehavior : Attribute, IServiceBehavior, IEndpointBehavior
{
public class SilverlightFaultMessageInspector : IDispatchMessageInspector
{
public void BeforeSendReply(ref Message reply, object correlationState)
{
Contract.Assume(reply !=null );
if (reply.IsFault)
{
HttpResponseMessageProperty property = new HttpResponseMessageProperty();
// Here the response code is changed to 200.
property.StatusCode = System.Net.HttpStatusCode.OK;
Contract.Assume(reply.Properties != null);
reply.Properties[HttpResponseMessageProperty.Name] = property;
}
}
public object AfterReceiveRequest(ref Message request, IClientChannel channel, InstanceContext instanceContext)
{
// Do nothing to the incoming message.
return null;
}
}
#region IServiceBehavior Members
void IServiceBehavior.AddBindingParameters(ServiceDescription serviceDescription, ServiceHostBase serviceHostBase, Collection<ServiceEndpoint> endpoints, BindingParameterCollection bindingParameters)
{
}
void IServiceBehavior.ApplyDispatchBehavior(ServiceDescription serviceDescription, ServiceHostBase serviceHostBase)
{
Contract.Assume( serviceHostBase != null);
Contract.Assume(serviceHostBase.ChannelDispatchers != null);
foreach (ChannelDispatcher cDispatcher in serviceHostBase.ChannelDispatchers)
{
Contract.Assume(cDispatcher != null);
Contract.Assume(cDispatcher.Endpoints != null );
foreach (EndpointDispatcher endpointDisbatcher in cDispatcher.Endpoints)
{
Contract.Assume(endpointDisbatcher != null);
Contract.Assume(endpointDisbatcher.DispatchRuntime != null);
Contract.Assume(endpointDisbatcher.DispatchRuntime.MessageInspectors != null);
endpointDisbatcher.DispatchRuntime.MessageInspectors.Add(new SilverlightFaultMessageInspector());
}
}
}
void IServiceBehavior.Validate(ServiceDescription serviceDescription, ServiceHostBase serviceHostBase)
{
}
#endregion
#region IEndpointBehavior Members
void IEndpointBehavior.AddBindingParameters(ServiceEndpoint endpoint, BindingParameterCollection bindingParameters)
{
}
void IEndpointBehavior.ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
{
}
void IEndpointBehavior.ApplyDispatchBehavior(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher)
{
Contract.Assume(endpointDispatcher != null);
Contract.Assume(endpointDispatcher.DispatchRuntime != null);
Contract.Assume(endpointDispatcher.DispatchRuntime.MessageInspectors != null);
SilverlightFaultMessageInspector inspector = new SilverlightFaultMessageInspector();
endpointDispatcher.DispatchRuntime.MessageInspectors.Add(inspector);
}
void IEndpointBehavior.Validate(ServiceEndpoint endpoint)
{
}
#endregion
}
然后，您需要定义将出现在 web.config 中的元素，比如这个
public class FaultHandlerElement : BehaviorExtensionElement
{
protected override object CreateBehavior()
{
return new FaultBehavior();
}
public override Type BehaviorType
{
get { return typeof(FaultBehavior); }
}
}
然后在 Web 配置中，您需要将其添加到服务模型部分 - 故障异常下面会有一条波浪线；)
<system.serviceModel>
<extensions>
<behaviorExtensions>
<add name="faultBehaviourExtension"
type="CopSilverlight.Web.FaultHandlerElement, CopSilverlight.Web, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/>
</behaviorExtensions>
</extensions
然后你把你的行为联系起来像这样使用它
<serviceBehaviors>
<behavior name="basicHttpBehaviour">
<serviceMetadata httpGetEnabled="true" />
<serviceDebug includeExceptionDetailInFaults="true" />
<faultBehaviourExtension />
</behavior>
另一种“修复”是在您的 wcf 服务中打开跟踪
需要注意的是，如果您不创建目录，它将根本不会产生日志
<system.diagnostics>
<sources>
<source name="System.ServiceModel"
switchValue="Information, ActivityTracing"
propagateActivity="true">
<listeners>
<add name="traceListener"
type="System.Diagnostics.XmlWriterTraceListener"
initializeData="c:\logs\appName\wcf.svclog" />
</listeners>
</source>
</sources>
</system.diagnostics>
但是，日志记录并不理想-第一个解决方案实际上解决了问题。
我已经实现了这两个，现在我得到了异常冒泡到我的silverlight应用程序，正如你所期望的那样。
关于silverlight - 10 秒后客户端异步 WCF 调用超时，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/3732516/