"The underlying connection was closed: An unexpected error occurred on a receive." in wcf

Question

1.00/5 (3 votes)

See more:

hi friendz,
i am getting the huge amount of data(Contacts) from Sql server..i am getting the following error...

Error:

An error occurred while receiving the HTTP response to http://localhost:8732/Design_Time_Addresses/ICloudServices/ContactService/. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

{"The underlying connection was closed: An unexpected error occurred on a receive."}

My wcf web.config file:

XML

<service name="ICloudServices.ContactService">
   <endpoint address="" binding="basicHttpBinding" contract="ICloudServices.IContactService">
     <identity>
       <dns value="localhost" />
     </identity>
   </endpoint>
   <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
   <host>
     <baseAddresses>
       <add baseAddress="http://localhost:8732/Design_Time_Addresses/ICloudServices/ContactService/" />
     </baseAddresses>
   </host>
 </service>

XML

<bindings>
    <basicHttpBinding>
      <binding name="basicHttpBindingSettings"  openTimeout="00:01:00" receiveTimeout="05:00:00" sendTimeout="05:00:00" maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" messageEncoding="Text">
        <readerQuotas maxDepth="128" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
      </binding>
    </basicHttpBinding>
  </bindings>
  <behaviors>
    <serviceBehaviors>
      <behavior>
        <dataContractSerializer maxItemsInObjectGraph="2147483647" />

        <!-- To avoid disclosing metadata information,
        set the value below to false and remove the metadata endpoint above before deployment -->
        <serviceMetadata httpGetEnabled="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="False" />
      </behavior>
    </serviceBehaviors>
  </behaviors>

Thanks in advance

Posted 4-Jul-12 1:31am

.net333

Add a Solution

Comments

[no name] 4-Jul-12 7:40am

Are the answers you are getting for a similar question you obviously posted with another account (http://www.codeproject.com/Questions/415508/The-underlying-connection-was-closed-An-unexpected) not good enough?

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Libish Varghese Jacob · Answer 1 · 2012-07-05T20:51:00

Here this kind of exception can happen if your receiveTimeout is not large enough.
Here in your configuration, you are setting

C#

receiveTimeout="05:00:00"

in "binding name="basicHttpBindingSettings" " but you are not associating it with your end point.
Either remove the name attribute from the binding so that basicHttpBinding will use it as default binding configuration. Or add

C#

bindingConfiguration="basicHttpBindingSettings"

to your basicHttpBinding endpoint. Hope this will work.

Sushil Mate · Answer 2 · 2012-07-04T01:46:00

Solution 1

Try this link.[^]

Posted 4-Jul-12 1:46am

Sushil Mate