Databases
StackOverflow2013
Postsdbo
POCommunicationException when Converting WCF Service from WsHttpBinding to NetTcpBinding
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCommunicationException when Converting WCF Service from WsHttpBinding to NetTcpBinding
    primarykey
    data
    text
    <p>I have a self hosted .Net 4.0 WCF service that I'm trying to convert from WsHttpBinding to NetTcpBinding for performance reasons. The service works just fine with the WsHttpBinding.</p> <p>Strangely enough, The service seems to work after switching to NetTcpBinding. (The service posts messages to a enterprise messaging system, and the message is posted and the client receives no error) however the following error is written to the server log:</p> <pre><code>Error: Service: MessageSenderService, Details: 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 '10675199.02:48:05.4775807'. ---&gt; System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.ServiceModel.Channels.SocketConnection.HandleReceiveAsyncCompleted() at System.ServiceModel.Channels.SocketConnection.BeginReadCore(Int32 offset,Int32 size, TimeSpan timeout, WaitCallback callback, Object state) --- End of inner exception stack trace --- at System.ServiceModel.Channels.SocketConnection.BeginReadCore(Int32 offset,Int32 size, TimeSpan timeout, WaitCallback callback, Object state) at System.ServiceModel.Channels.TracingConnection.BeginRead(Int32 offset, Int32 size, TimeSpan timeout, WaitCallback callback, Object state) at System.ServiceModel.Channels.SessionConnectionReader.BeginReceive(TimeSpan timeout, WaitCallback callback, Object state) at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.PerformOperation(TimeSpan timeout) at System.ServiceModel.Channels.SynchronizedMessageSource.SynchronizedAsyncResult`1..ctor(SynchronizedMessageSource syncSource, TimeSpan timeout, AsyncCallback callback, Object state) at System.ServiceModel.Channels.TransportDuplexSessionChannel.BeginReceive(TimeSpan timeout, AsyncCallback callback, Object state) at System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceiveAsyncResult..ctor(TransportDuplexSessionChannel channel, TimeSpan timeout, AsyncCallback callback, Object state) at System.ServiceModel.Channels.TransportDuplexSessionChannel.BeginTryReceive(TimeSpan timeout, AsyncCallback callback, Object state) at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.BeginTryReceive(TimeSpan timeout, AsyncCallback callback, Object state) </code></pre> <p>Again, no error occurs on the server log when using the WsHttpBinding.</p> <p>Server Config:</p> <pre><code> &lt;service behaviorConfiguration="debugEnabled" name="My.Service"&gt; &lt;endpoint address="" binding="netTcpBinding" bindingConfiguration="netTcpBindingConfig" contract="My.Service.Contract" /&gt; &lt;endpoint address="mex" binding="mexTcpBinding" contract="IMetadataExchange" /&gt; &lt;/service&gt; .... &lt;behaviors&gt; &lt;serviceBehaviors&gt; &lt;behavior name="debugEnabled"&gt; &lt;serviceDebug includeExceptionDetailInFaults="true" /&gt; &lt;serviceThrottling maxConcurrentSessions="200" maxConcurrentCalls="500" maxConcurrentInstances="200"/&gt; &lt;serviceMetadata httpGetEnabled="true" /&gt; &lt;dataContractSerializer maxItemsInObjectGraph="2147483647"/&gt; &lt;/behavior&gt; &lt;/serviceBehaviors&gt; &lt;/behaviors&gt; .... &lt;bindings&gt; &lt;netTcpBinding&gt; &lt;binding name="netTcpBindingConfig" maxReceivedMessageSize="5242880" closeTimeout="00:01:00" receiveTimeout="00:01:00" sendTimeout="00:01:00" openTimeout="00:01:00"&gt; &lt;readerQuotas maxArrayLength="5242880" /&gt; &lt;security mode="None" /&gt; &lt;/binding&gt; &lt;/netTcpBinding&gt; &lt;/bindings&gt; </code></pre> <p>We build the client binding in code, not config. That looks like this:</p> <pre><code>return new NetTcpBinding(SecurityMode.None, reliableSessionEnabled) { MaxBufferPoolSize = Int32.MaxValue, MaxReceivedMessageSize = Int32.MaxValue, ReaderQuotas = new XmlDictionaryReaderQuotas { MaxArrayLength = Int32.MaxValue, MaxDepth = Int32.MaxValue, MaxStringContentLength = Int32.MaxValue }, ReceiveTimeout = TimeSpan.FromMinutes(1.0), CloseTimeout = TimeSpan.FromMinutes(1.0), OpenTimeout = TimeSpan.FromMinutes(1.0), SendTimeout = TimeSpan.FromMinutes(1.0) }; </code></pre> <p>Any ideas out there?</p> <p>EDIT: I would like to add that I see the error on every call to the service, not only under load. The request and response messages are very small so it likely not related to message size. The error is written almost instantaneously, so it it not a timeout problem.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjohnmcase
    1. USjohnmcase
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCommunicationException when Converting WCF Service from WsHttpBinding to NetTcpBinding
      1. This table or related slice is empty.
      1. VTUpMod
    1. COReceiveTimeout 1 minute ofthen is too short, so your connection will be terminated after 1 minute being active
      singulars
      1. POCommunicationException when Converting WCF Service from WsHttpBinding to NetTcpBinding
      1. USsll
    2. COThe error happens immediately, I am definitely not hitting a 1 minute timeout.
      singulars
      1. POCommunicationException when Converting WCF Service from WsHttpBinding to NetTcpBinding
      1. USjohnmcase
    3. COSo enable WCF Trace logs with `switchValue="All"` there you might find more details
      singulars
      1. POCommunicationException when Converting WCF Service from WsHttpBinding to NetTcpBinding
      1. USsll
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload