Wcf error on client - long stored procedure

Question

0.00/5 (No votes)

See more:

Hi,

I have a c# win project that uses a wcf service to connect the SQL SERVER 2008R2.
When the service calls to a long stored procedure, after ~10 minutes the client throw this exception:

C#

Error in mscorlib Message: The communication object, System.ServiceModel.Security.SecuritySessionClientSettings`1+ClientSecurityDuplexSession
Channel[System.ServiceModel.Channels.IDuplexSessionChannel]

I looked on the SQL profiler and saw that the SQL server is continuing run the SP and the error was just in the client side.

Do you have a suggestion why it happened?

(It occurred just on the production, in the DEV the service and the application in the same server and it doesn't occurred)

Thanks,
Efrat

EDIT:

I have a contract that use [ServiceContract] and [OperationContract].
The service class implement the contract

Client App.Config

XML

<endpoint address="net.tcp://localhost/Services/Service.svc"
       binding="netTcpBinding" bindingConfiguration="NetTcpBinding" behaviorConfiguration="normal"
       contract="Services.Contracts.IService" name="IService">
     <identity>

Server Web.Config

XML

<service name="Services.Service" behaviorConfiguration="Service1Behavior">
       <endpoint address="" binding="netTcpBinding" bindingConfiguration="tcpBinding.WindowsAuth" contract=".Services.Contracts.IService" behaviorConfiguration="epNormal">
       </endpoint>
       <host>
         <baseAddresses>
           <add baseAddress="net.tcp://localhost/Services/" />
         </baseAddresses>
       </host>
     </service>

What I have tried:

I tried to restore the bug in DEV so I set the idle in the IIS to less than the SP run, after this time there was an exception in the client but also the SQL SERVER stopped run the SP.

Posted 14-Feb-16 22:18pm

Member 8092498

Updated 14-Feb-16 23:26pm

v3

Add a Solution

1 solution

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)

Manas_Kumar · Answer 1 · 2016-02-14T22:37:00

Add following code when you are calling WCF service:

C#

using(WCFServiceClient client = new WCFServiceClient ())
{ 
    // 15 minutes 30 seconds
    client.Endpoint.Binding.SendTimeout = new TimeSpan(0, 15, 30); 
}

or
For a client, you would want to adjust the sendTimeout attribute of a binding element. For a service, you would want to adjust the receiveTimeout attribute of a binding element.

XML

<system.serviceModel>
  <bindings>
    <netTcpBinding>
      <binding name="longTimeoutBinding"
        receiveTimeout="00:10:00" sendTimeout="00:10:00">
        <security mode="None"/>
      </binding>
    </netTcpBinding>
  </bindings>

receiveTimeout - It includes receiving a reply message for a request/reply service operation. This timeout also applies when sending reply messages from a callback contract method.

sendTimeout - Gets or sets the interval of time that a connection can remain inactive, during which no application messages are received, before it is dropped.

It is in Hour:Minute:Second format.

Secondly you need to improve performance of execution of StoredProcedure. It is not good to execute a stored proc as 10 minutes. So just see execution plan and add find out where it is taking time. You can add some non-clustered index to tables or optimize your select query.

SQL Profiler and SQL Tuning Advisor[^]