Note that there are some explanatory texts on larger screens.

plurals
  1. POWCF Tracing. How I can get the exact reason for closing connection?
    primarykey
    data
    text
    <p>In my WCF service, when trying transfer large data I constantly get an error: <strong><em>The underlying connection was closed: The connection was closed unexpectedly</em></strong></p> <p>I want to know what particular reason invokes this error, so I set up <strong>WCF Tracing</strong> and can read <em>traces.svclog</em> file.</p> <p>The problem is, that I can see in this file a lot of information about flow of processes, I can see exact time when exception is appeared, but I can't see the exact reason for that. Is it due to <strong><em>MaxReceivedMessageSize</em></strong> or something like that. </p> <p>Is it so that <em>traces.svclog</em> can not contain such information or am I doing something wrong? </p> <p>How such information could be obtained?</p> <p><strong>Edited (added):</strong></p> <p>From my server-side app.config:</p> <pre><code> &lt;system.serviceModel&gt; &lt;bindings&gt; &lt;basicHttpBinding&gt; &lt;binding name="NAVBinding_ICustomer_Service" closeTimeout="01:50:00" openTimeout="01:50:00" receiveTimeout="01:50:00" sendTimeout="01:50:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="2147483647" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"&gt; &lt;readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /&gt; &lt;security mode="None"&gt; &lt;transport clientCredentialType="None" proxyCredentialType="None" realm="" /&gt; &lt;message clientCredentialType="UserName" algorithmSuite="Default" /&gt; &lt;/security&gt; &lt;/binding&gt; &lt;/basicHttpBinding&gt; &lt;/bindings&gt; &lt;services&gt; &lt;service name = "Customer_Service" behaviorConfiguration="returnFaults"&gt; &lt;endpoint name="NAVBinding_ICustomer_Service" address = "http://localhost:8000/nav/customer" binding = "basicHttpBinding" bindingConfiguration= "NAVBinding_ICustomer_Service" contract = "NAVServiceReference.ICustomer_Service"/&gt; &lt;/service&gt; &lt;/services&gt; &lt;behaviors&gt; &lt;serviceBehaviors&gt; &lt;behavior name="returnFaults" &gt; &lt;serviceDebug includeExceptionDetailInFaults="true" /&gt; &lt;serviceMetadata httpGetEnabled="true" /&gt; &lt;/behavior&gt; &lt;/serviceBehaviors&gt; &lt;/behaviors&gt; &lt;/system.serviceModel&gt; </code></pre> <p><strong>Edited (added):</strong></p> <p>What is the right and best way to turn WCF service from a "black box" to an easily troubleshooted service, which tells the reason why something goes not the expected way? What tools, techniques you use to troubleshoot WCF service?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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