On Sat, May 1, 2010 at 9:29 PM, Omatase <[email protected]> wrote: > I have a service made with .Net 2.0 Web Services that needs to > receive > large SOAP packets (~1MB). When I try to send these packets to the > web > service in production I get this error: "An existing connection was > forcibly closed by the remote host". And in the IIS server logs I > get: > "2010-04-27 11:27:23 10.200.130.0 2792 10.200.0.121 80 HTTP/1.1 > POST / > Application/Service.asmx - 544861399 Connection_Dropped > ApplicationAppPool". > > I have reproduced the configuration and data in development to > reproduce the problem but it never fails in development. Even if I > increase the file size to 2.5MB it does not have the same error > message. > > Does anyone know what I can do to troubleshoot this or what measures > I > could take to make my web service work better with large SOAP > packets? > I have already set the executionTimeout and maxRequestLength on the > client but those shouldn't be a factor anyway since it works in one > environment and not the other. > > Here is a sample of the SOAP packets I am sending (although the > packets in question will have about 26000 lines): > > http://dotnetdevelopment.pastebin.com/YNqnsEZ1 ------------------------
I would stream a zip file instead of all that soap. Is your soap jason? You might get a huge reduction in your filesize depending on your schema and the length of a column's name. -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell
