使用管道时，AppDashboard中AppFabric错误下的工作流程4错误

Question

我已经成功获得了一些使用Server AppFabric的工作流程。

但是我注意到，但是当我尝试使用namePipeBinding与工作流进行通信时，该调用对客户端成功工作（调用在服务的接口定义中标记为IsOneWay = true），但在AppFabric的仪表板，我可以看到该消息被成功处理，然后我们得到显示为“服务异常”除了具有以下不同

System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.IOException: The write operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). 
at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes) 
--- End of inner exception stack trace --- 
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) 
at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.End(IAsyncResult result) 
at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult) 
--- End of inner exception stack trace --- 
at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult) 
at System.ServiceModel.Channels.StreamConnection.EndRead() 
--- End of inner exception stack trace --- 
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) 
at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult.End(IAsyncResult result, Message& message) 
at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext) 
at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) 

工作流由两个接收活动的呼叫，但它不具有任何receiveandsendreply activitiies 。

当我使用http绑定时，一切正常。

为什么在仪表板中报告此错误？

的客户端应用程序配置的详细信息显示如下

<system.serviceModel> 
    <bindings> 
     <basicHttpBinding> 
      <binding name="BasicHttpBinding_ISLG" closeTimeout="00:01:00" 
       openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" 
       allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" 
       maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" 
       messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" 
       useDefaultWebProxy="true"> 
       <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" 
        maxBytesPerRead="4096" maxNameTableCharCount="16384" /> 
       <security mode="None"> 
        <transport clientCredentialType="None" proxyCredentialType="None" 
         realm="" /> 
        <message clientCredentialType="UserName" algorithmSuite="Default" /> 
       </security> 
      </binding> 
     </basicHttpBinding> 
     <netNamedPipeBinding> 
      <binding name="NetNamedPipeBinding_ISLG" closeTimeout="00:01:00" 
       openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" 
       transactionFlow="false" transferMode="Buffered" transactionProtocol="OleTransactions" 
       hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="524288" 
       maxBufferSize="65536" maxConnections="10" maxReceivedMessageSize="65536"> 
       <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" 
        maxBytesPerRead="4096" maxNameTableCharCount="16384" /> 

       <security mode="Transport"> 
        <transport protectionLevel="EncryptAndSign"/> 
       </security> 
      </binding> 
     </netNamedPipeBinding> 
    </bindings> 
    <client> 
     <endpoint address="net.pipe://vm-vsnet2010/TestWorkflowDeclarativeServiceLibrary/Service3.xamlx" 
      binding="netNamedPipeBinding" bindingConfiguration="NetNamedPipeBinding_ISLG" 
      contract="SLGService.ISLG" name="NetNamedPipeBinding_ISLG"> 
      <identity> 
       <servicePrincipalName value="host/VM-VSNET2010" /> 
      </identity> 
     </endpoint> 
    </client> 
</system.serviceModel> 

Answer 1

可以提交服务器绑定配置？它们可能不同，这就是服务器无法从管道接收数据的原因。

Regards