WCF proxy ProcessGetResponseWebException on HttpChannelReque

本文关键字:HttpChannelReque on ProcessGetResponseWebException proxy WCF | 更新日期: 2023-09-27 18:36:44

ServiceContract

[OperationContract]
List<Campaign> AttainCampaigns();

直接实例化对象时工作

public List<Campaign> AttainCampaigns()
{
    var campaign1 = new Campaign { Id = "x", Name = "namex" };
    var campaign2 = new Campaign { Id = "y", Name = "namey" };
    var campaigns = new List<Campaign> { campaign1, campaign2 };
    return campaigns;
}

如果实体框架中的等效对象,则在客户端上引发错误

// Different implementation getting the campaign objects from database
private List<Campaign> RetrieveCampaigns()
{
    return Global.Repositor.Campaigns.Select(c => c).ToList();;
}
public static EntityRepositor Repositor
{
    get
    {
        if (_entityRepositor == null)
            _entityRepositor = new EntityRepositor();
        return _entityRepositor;
    }
}
public class EntityRepositor : DbContext
{
    public DbSet<Campaign> Campaigns { get; set; }
}

服务器上没有明显的错误

  • 奇怪的是,当我将调试器附加到服务器端的进程时,我没有看到任何异常 - 实体框架似乎很好地实例化了基础 SQL Express 数据库中的对象
  • 我什至没有在输出中看到任何第一次机会异常

WCF 测试客户端在大约 15 秒后出现异常,然后立即

  • 我第一次调用AttainCampaigns()客户端等待/处理大约 15 秒,然后显示以下异常
  • 所有后续调用都会立即显示错误,即使我删除服务并重新连接也是如此

_My猜测是数据库调用本身很好,但需要太长时间,所以我需要在服务器或客户端配置中增加某些超时值?如果这是正确的树下吠叫,它们可能是哪些超时?

An error occurred while receiving the HTTP response to http://example.com/Service.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Server stack trace: 
   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at IBacker.AttainCampaigns()
   at BackerClient.AttainCampaigns()
Inner Exception:
The underlying connection was closed: An unexpected error occurred on a receive.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
Inner Exception:
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)
Inner Exception:
An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

Server - perSession ServiceContract & Web.config

[ServiceBehavior(InstanceContextMode = InstanceContextMode.PerSession, 
ConcurrencyMode = ConcurrencyMode.Single)]

&

  <system.web>
    <compilation targetFramework="4.5" />
  </system.web>
  <system.serviceModel>     
    <bindings>
      <wsHttpBinding>
        <binding name="wsHttp" allowCookies="true">
          <security mode="None" />
        </binding>
      </wsHttpBinding>
    </bindings>
    <services>
      <service name="MyNameSpace.MyImplementation">
        <endpoint address="" binding="wsHttpBinding" bindingConfiguration="wsHttp"
          name="wsHttpEp" contract="MyNameSpace.IServiceContract" />
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior>
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true" />
    <directoryBrowse enabled="true" />
  </system.webServer>
  <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
  </entityFramework>

客户端 - ChannelFactory & App.config

_channelFactory = new ChannelFactory<T>("wsHttpEp");
Service = _channelFactory.CreateChannel();

&

  <system.serviceModel>
    <bindings>
      <wsHttpBinding>
        <binding name="wsHttp" allowCookies="true">
          <security mode="None" />
        </binding>
      </wsHttpBinding>
    </bindings>
    <client>
      <endpoint address="http://example.com/Service.svc" contract="MyNameSpace.IServiceContract"
                binding="wsHttpBinding" bindingConfiguration="wsHttp" name="wsHttpEp" />
    </client>
  </system.serviceModel>

WCF proxy ProcessGetResponseWebException on HttpChannelReque

您需要更新服务器配置文件才能在客户端中查看异常详细信息:

<serviceBehaviors>
   <behavior name="EmployeeManager_Behavior">
      <serviceDebug includeExceptionDetailInFaults="true"/>
      <serviceMetadata httpGetEnabled="true" />
   </behavior>
</serviceBehaviors>

请在启用该选项的情况下发布更新的异常详细信息。

看看你的代码,我可能会给你一个建议。不要存储静态变量DbContext。EntityFramework执行大量缓存,因此上下文实例化不需要任何成本。静态变量可以由某人处理,Null检查不会捕获它。