WCF client hangs on call with lots of data

Question

I have a WCF Service on an Azure VM and I have method that takes a lot of time on server side (depending on the size of data I send).

The problem is that sometimes my client hangs when this method is called. I know that the method completes and reaches the last line, but my client never gets a response. It happens when I'm passing a lot of data to that method and it takes like 1 hour to complete. If the method completes within several minutes the client successfully gets the response.

Here is my web.config

<?xml version="1.0"?>
<configuration>

  <configSections>

    <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
      <section name="PrintCloud.WebService.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
      <section name="PrintCloud.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/>
    </sectionGroup>
  </configSections>

  <system.diagnostics>

    <sources>
      <source propagateActivity="true" name="System.ServiceModel" switchValue="Warning,ActivityTracing">
        <listeners>
          <add type="System.Diagnostics.DefaultTraceListener" name="Default">
            <filter type=""/>
          </add>
          <add name="ServiceModelTraceListener">
            <filter type=""/>
          </add>
        </listeners>
      </source>
    </sources>
    <sharedListeners>
      <add initializeData="C:\Logs\PrintCloudLog.svclog" type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" name="ServiceModelTraceListener" traceOutputOptions="Timestamp">
        <filter type=""/>
      </add>
    </sharedListeners>
    <trace>
      <listeners>
        <add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener, Microsoft.WindowsAzure.Diagnostics, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" name="AzureDiagnostics">
          <filter type=""/>
        </add>
      </listeners>
    </trace>
  </system.diagnostics>
  <appSettings>
    <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true"/>
  </appSettings>

  <system.web>
    <compilation targetFramework="4.5" debug="true"/>
    <httpRuntime targetFramework="4.5"/>
    <customErrors mode="Off"/>
  </system.web>
  <system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="LargeSettings" maxBufferSize="2147483647" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" openTimeout="00:10:00" closeTimeout="00:10:00" sendTimeout="00:10:00" receiveTimeout="00:10:00" transferMode="Streamed">
          <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
        </binding>
      </basicHttpBinding>
    </bindings>
    <services>
      <service name="PrintCloud.PrintCloudService">
        <endpoint binding="basicHttpBinding" bindingConfiguration="LargeSettings"
          name="Default" contract="PrintCloud.PrintCloudService" />
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior>
          <!-- To avoid disclosing metadata information, set the values below to false before deployment -->
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/>
          <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
          <serviceDebug includeExceptionDetailInFaults="true"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <protocolMapping>
      <add binding="basicHttpsBinding" scheme="https"/>
    </protocolMapping>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="false" multipleSiteBindingsEnabled="true"/>
  </system.serviceModel>
  <system.webServer>
    <security>
      <requestFiltering>
        <requestLimits maxAllowedContentLength="2147483647" />
      </requestFiltering>
    </security>
    <modules runAllManagedModulesForAllRequests="true"/>
    <!--
        To browse web app root directory during debugging, set the value below to true.
        Set to false before deployment to avoid disclosing web app folder information.
      -->
    <directoryBrowse enabled="true"/>
  </system.webServer>

</configuration>

And client side config:

binding.OpenTimeout = new TimeSpan(100, 0, 0);
binding.CloseTimeout = new TimeSpan(100, 0, 0);
binding.SendTimeout = new TimeSpan(100, 0, 0);
binding.ReceiveTimeout = new TimeSpan(100, 0, 0);

There is no exceptions at all. Client simply does not get response from server.

Here is the method that I invoke:

public Domain.DocumentGenerationResponse GenerateDocument(Guid id, Domain.PrintOptions printOptions, Domain.Job job)

it returns only several short strings. job arguments contains 1000 documents (each document has an image 111Kb)

Please share your code with us so we can see what you're doing. — Yuval Itzchakov, Aug 14 '14 at 16:37
Does the client eventually throw a timeout? One thought is there may be a proxy server somewhere between you and the server that aborts/cancels the request after a certain amount of time. — mikey, Aug 14 '14 at 16:40
No it already hangs for 3 hours and there is no exceptions. @mikey — Stanislav Chernychko, Aug 14 '14 at 17:07
Doesn't Azure cut idle connections after a while? Like 20min? — usr, Aug 14 '14 at 18:12

score 0 · Answer 1 · edited May 23 '17 at 11:57

0

You should check for timeouts or message size configurations. Check this MSDN link for timeout configuration and this link for message quota size configuration.

edited May 23 '17 at 11:57

Community

1
1

answered Aug 14 '14 at 16:50

Abhay Kumar

833
3
11
24

WCF client hangs on call with lots of data

1 Answers1