views:

196

answers:

1

Apparently i start getting this error if i try to transfer any file over 50 mb, I am using WCF, need help urgently. I have webservices written in Java / tomcat. could it be that problem in serverside configurations. The server is tom cat , can you tell me which value to customize in that case

<bindings>
  <basicHttpBinding>
    <binding name="MyWebService1SoapHttpPortBinding" closeTimeout="00:01:00"
        openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:11:00"
        allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
        maxBufferSize="4000000" maxReceivedMessageSize="99999999"
        messageEncoding="Mtom" textEncoding="utf-8" transferMode="StreamedRequest"
        useDefaultWebProxy="true">
     <security mode="None">
        <transport clientCredentialType="None" proxyCredentialType="None"
            realm="" />
        <message clientCredentialType="UserName" algorithmSuite="Default" />
      </security>
    </binding>
  </basicHttpBinding>
</bindings>
<client>
  <endpoint address="http://[IP]/Transfer"
      binding="basicHttpBinding" bindingConfiguration="MyWebService1SoapHttpPortBinding"
      contract="Transfer" name="MyWebService1SoapHttpPort" />
</client>
+1  A: 

If you take your error message and google it you will find many answers.

A TCP error (10055: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full)

Here is one. http://support.microsoft.com/kb/196271

Romain Hippeau
Thanks Romain , If googling would be effective in this case , i wouldnt be here, still i want to know how can i avoid this error , and still transfer the data over webservices to Java. I have a WCF server and a client and they works perfect even for 250 mb transfer, yet as soon as i shift my solution to Java webservices i start getting error even at 50 mb. I am sure i am using right DataHandler type as per metro , Jax-ws. Anyway I wish there is any expert opinion.Thanks for you answer
I believe its interoperability which causing problem between Java and WCF