WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

Hi Guys

I have been pulling my hair out trying to fix an issue with sending data over WCF, I have read pretty much every THREAD on this forum regarding or similar to this issue without any successful solution.

I have a simple data object which has a [DataMember] with a data type of byte[]. I use this to send binary data from my web app as follows:

Asp.net MVC website --> WCF Client (Has my Service References) --> My Services (MyServices.svc) --> Business/Data Tier

Everything is being executed from within VS 2008 Pro.

Now I have successfully sent data up to 2.2MB, however it fails if i try and send a file such as 2.3MB or larger i get the following exceptions:

General Exception

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at SoftApp.WCFClient.MyServiceReference.IMyService.Document_Save(DtoDocument dtoDocument, Int32 usercode)
   at SoftApp.WCFClient.MyServiceReference.MyServiceClient.Document_Save(DtoDocument dtoDocument, Int32 usercode) in c:\dev\softapp\softapp.wcfclient\service references\myservicereference\reference.cs:line 167
   at SoftApp.WebsiteServices.MyService.Document_Save(DtoDocument dtoDocument, Int32 usercode) in C:\Dev\SoftApp\SoftApp.WebsiteServices\MyService.cs:line 146
   at SoftApp.Website.Controllers.CaseController.EditDocument(Int32 id, String description, String unique, String filename) in C:\Dev\SoftApp\SoftApp.Website\Controllers\CaseController.cs:line 422

An error occurred while receiving the HTTP response to http://localhost:9002/MyService.svc. 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.

Inner Exceptions - Parent/Child Order

InnerException {"The underlying connection was closed: An unexpected error occurred on a receive."} System.Exception {System.Net.WebException}

InnerException {"Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."} System.Exception {System.IO.IOException}

InnerException {"An existing connection was forcibly closed by the remote host"} System.Exception {System.Net.Sockets.SocketException}

MyService.svc - web.config

WCF Client - app.config

MVC Website - web.config

I have also added the following to the we.config as suggested by another Post.

I really need to get this sorted, I have searched the entire Web and can't find a solution. Any help would be really appreciated!

Maybe if we can all put our brains together and work on resolving this, we can help many others too as it seems a lot of people are experiencing similar problems.

Thanks in advance!

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

Are you going through a proxy server?

Need to see the way you open the connection and the format the data when you send.

2.3 megs is not that large, and should go quick with a fast connection.

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

I am not using a proxy server, i am just running this solution within VS 2008 Pro. I agree 2.3mb is not very large at all.

I just reference the WcfServiceLibrary which has all my Service references i.e. Http://localhost:9002/MyService.svc

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

I've never used wcf, because I've always been kind or skeptical of some of their easy to use technology. There always seems to be a price to pay for ease of programming and use.

What does your project do?, I'm just curious.

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

This app makes up the document management side of a larger development targeted at the legal industry.

Is there anyone out there who knows how to fix this issue, any Microsoft WCF Employee's...... come on???????????????

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

I'm no Microsoft expert but I've been having the same problems as you. I've tried little bits and pieces of suggestions from many different blogs but I'll tell you what I did to my Web.config to get this going.

Strange part about all of this is that I had no problems when I ran the code on my own computer using ASP.NET Development Server. It's only when I published to IIS 7.0 on a dedicated web server that I started gettings problems with the size of the data files.

My service takes a flat data file, converts in to a dataset, and transports the dataset to a SQL 2008 database table. I could transfer up to 4000 records but anything larger than that got the error.

It's hard to determine exactly how large a dataset would be in memory but I ran a query of 4000 records from this table, copied to notepad and it produced a file of 2.025MB. 5000 records would fail. Copying these records to notepad produced a file sized 2.521MB. Sounds familiar?

First, I tweaked the bindings. Here are the items I changed...anwhere you see these properties, client or server section in the web.config, change them.

maxBufferPoolSize="524288" maxReceivedMessageSize="2147483647" maxDepth="999" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"

Next, I tweaked the <Behaviors> section...I added what you see below.

<endpointBehaviors><behavior name="customQuotaBehavior">dataContractSerializer maxItemsInObjectGraph="2147483647"/></behavior></endpointBehaviors>

Make sure sure add this behavior confguation to your service endpoint...

behaviorConfiguration="customQuotaBehavior"

Finally, and quite possibly the most important in the <httpRuntime> in the system.web section. The maxRequestLength probably the most important...

I wish I could tell you the exact change to the web.config that made it work but I don't really know. I don't think anyone does!...even the Microsoft experts.

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

Thanks for your input, i'll try this first thing tomorrow and feedback asap.

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

Sorry for the delay in feedback. I have tried what you suggested and still i get the same issue.

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

Hi I'm wondering, do you finally find a solution to this problem?

I've got the same problem right now. I'm gonna try the solution proposed here. But I have no hope it works... Since 3 days I've modified all the config files without any change.

So if you find a solution, please let me know

thanks!

(sorry for my english, this is not my mother tong ;) )

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

I am using the same solution and having the same issue as you did.

Did you actually solve this problem?

Why having problem sending data larger than 2.2M, I had increased all the size limitations.

Anyone get a solution?

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

Solved by increasing maxRequestLength on wcf service server side web.config

Re: WCF issues sending large data - "An existing connection was forcibly closed by the remote host"

In my case the following solved it

On the server side, increase the size of maxItemsInObjectGraph

<div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"><behaviors></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> <serviceBehaviors></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> <behavior name="ServiceBehavior"></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> <dataContractSerializer maxItemsInObjectGraph ="2147483647"/></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> <serviceThrottling</div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> maxConcurrentCalls="16"</div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> maxConcurrentInstances="26"</div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> maxConcurrentSessions="10"</div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> /></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> </behavior></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> </serviceBehaviors></div> <div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;" id="_mcePaste"> </behaviors></div>

<serviceThrottling

maxConcurrentCalls="16"

maxConcurrentInstances="26"

maxConcurrentSessions="10"

</behavior>

</serviceBehaviors>

</behaviors>

On the client side, make sure to specify the same behavior:

<dataContractSerializer maxItemsInObjectGraph="2147483647"/>

</behavior>

</endpointBehaviors>

</behaviors>