WCF timeout error on larger files, even though the file transfers successfully

I have a WCF service that transfers a file from client to server.  It works fine if the file is very small, but if the size is over 16k, it still transfers just fine, but gives me this error:

The request operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.

I am using a custom binding:

<customBinding>
        <binding name="CustomBinding_IMySvc" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00">
          <binaryMessageEncoding>
            <readerQuotas maxArrayLength="10485760"/>
          </binaryMessageEncoding>
          <reliableSession acknowledgementInterval="00:00:00.2000000" maxTransferWindowSize="32" inactivityTimeout="00:10:00" maxPendingChannels="128" maxRetryCount="8" ordered="true"/>
          <security authenticationMode="UserNameOverTransport"/>
          <httpsTransport authenticationScheme="Anonymous" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" proxyAuthenticationScheme="Anonymous" realm=""
                          useDefaultWebProxy="true" maxReceivedMessageSize="10485760"/>
        </binding>
      </customBinding>


And the following errors show up on a trace listener:

The communication object, System.ServiceModel.Channels.ReliableReplySessionChannel, cannot be used for communication because it has been Aborted.
The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.

Any advice appreciated.
BRNIITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Aaron JabamaniTechnical ArchitectCommented:
It is idle to keep everything to same value like receivetimeout like below

 <binding name="CustomBinding_IMySvc" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00">
0
BRNIITAuthor Commented:
Tried this, still exact same error.  File copies up to server just fine, but it does not close after the copy is done, it just waits for that 00:01:00 to expire (even though I have changed the timeouts as you suggested to 00:10:00) then gives this timeout error message.
0
BRNIITAuthor Commented:
I figured this out.  I am using transferMode="Buffered" so apparently if the file was larger than the buffer size, it would still transfer somehow but the client does not close gracefully.  Increasing maxReceivedMessageSize and maxBufferSize solved the problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
WCF

From novice to tech pro — start learning today.