WCF/BizTalk 2006/R2 – The Connection was closed unexpectedly

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › WCF/BizTalk 2006/R2 – The Connection was closed unexpectedly

Viewing 1 reply thread
  • Author
    Posts
    • #20616

      I’m running on a Virtual PC (VMWare/LabManager). Other peoples virtual machines seem to run simple WCF/Database queries in 2 seconds, while mine takes 20.  But anyway, I loaded 200 records, and have set the WCF timeouts all to 30 minutes.
      I was getting timeouts, so I bumped it up huge.  Now I’m getting the following:

      Event Type: Error
      Event Source: BizTalk Server 2006
      Event Category: BizTalk Server 2006
      Event ID: 5754
      Date:  9/5/2008
      Time:  3:03:59 PM
      User:  N/A
      Computer: Dev-XP-BZWRK-01
      Description:
      A message sent to adapter “WCF-WSHttp” on send port “WCF_TDS_UpdateLoan_RequestResponse” with URI “http://localhost/TMAC.ESB.Web.WebServices.TDSWebService/TDSWEBService.svc” is suspended.
       Error details: System.ServiceModel.CommunicationException: The underlying connection was closed: The connection was closed unexpectedly. —> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
         at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
         at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
         — End of inner exception stack trace —

      Server stack trace:
         at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
         at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
         at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
         at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)

      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 System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
         at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)
       MessageId:  {A3207863-0B8D-453C-B6AD-E5806C910F34}
       InstanceID: {2A808372-3E80-4C35-8D0A-4A3AB7E89277}

       

      Any ideas?
      Thanks,
      Neal Walters

       

    • #20619

      Lots of times a “connection was closed” error means that an exception occurred in the service you were calling.  Does the service log exceptions?

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.