Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could check your configuration file for a size quotas in your binding.</p> <pre><code>&lt;basicHttpBinding&gt; &lt;binding name="BasicHttpBinding_ForgotPasswordService" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"&gt; &lt;readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" /&gt; &lt;/binding&gt; &lt;/basicHttpBinding&gt; </code></pre> <p>There could could adjust <code>maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536"</code> to your needs.</p> <p>But in <strong>your individual case</strong> I would preferably consider the streaming capabilities of WCF like here: "<a href="http://msdn.microsoft.com/en-us/library/ms733742.aspx" rel="nofollow">Large Data and Streaming in WCF</a>" (MSDN)</p> <p><strong>[EDIT]</strong></p> <p>Thinking about it, if you had hit the quota limits, the exception would most likely be different and tell it you like "The maximum array length quota has been exceeded" or something similar.</p> <p>An <code>OutOfMemoryException</code> is might have more to do with the actual limits of at least one of the communicating systems. A possibly cause might be some <strong>memory leak</strong> stuffing data into RAM and not cleaning up properly (or fast enough).</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.
    1. This table or related slice is empty.
    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