Timeout Error

Timeout Error

Postby fernando.tellfree » Fri 25 Mar 2011 20:21

I am getting the timeout error in the processing procedure,
after more than 30 seconds being that I increased the timeout.

Gives error stating whether or not contexto.CommandTimeout

I'm using the latest version 6.10.126.0

The connection string are to:
Code: Select all
Connection Timeout=15;Default Command Timeout=0;Connection Lifetime=0;

          providerName="System.Data.EntityClient" />


Error:
Code: Select all
EntityException An error occurred while executing the command definition.
See the inner exception for details. - Lost connection to MySQL server during query


Code: Select all
            using (var contexto = new PortabilidadeEntities())
            {
                contexto.CommandTimeout = 7200;
                contexto.ProcAtualizaPortabilidadeRota(DateTime.Now);
            }


Log:
Code: Select all
3/25/2011 4:00:16 PM - ProcAtualizaPortabilidadeRota - Data = 3/24/2011
3/25/2011 4:00:46 PM - EntityException An error occurred while executing the command definition. See the inner exception for details. - Lost connection to MySQL server during query
fernando.tellfree
 
Posts: 4
Joined: Fri 25 Mar 2011 19:42

Postby Shalex » Tue 29 Mar 2011 15:21

Does this error arise after 30 seconds of executing?

I cannot reproduce the problem with a simple stored procedure using dotConnect for MySQL v 6.10.126 in our environment. Please give us the following information:
1) the version of your MySQL server;
2) send us a small test project with the corresponding DDL/DML script.
Shalex
Devart Team
 
Posts: 7391
Joined: Thu 14 Aug 2008 12:44

Postby fernando.tellfree » Wed 30 Mar 2011 12:59

The simulation project was sent.
This project is implementing a procedure that simulates this error.
The procedure has only select sleep (60), to simulate the processing that exceeds 30 seconds.

This type of problem also occurs through the linq queries.

The simulation project was sent.

The version of MySQL is 5.1.48-a-log
The server is Windows 2003
The Visual Studio is 2010
fernando.tellfree
 
Posts: 4
Joined: Fri 25 Mar 2011 19:42

Postby AndreyR » Thu 31 Mar 2011 08:33

Thank you for the project, I have reproduced the problem.
As a temporary workaround, add ";Default Command Timeout=7200" to your context connection string.
I will let you know when the problem is fixed.
AndreyR
Devart Team
 
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Postby AndreyR » Fri 22 Apr 2011 12:32

The latest 6.30.145 Beta build of dotConnect for MySQL is available here (the trial version) or from Registered Users' Area (provided that you have an active subscription).
The problem with command timeouts is fixed in it.
For more information about the fixes and improvements available in dotConnect for MySQL Beta, please refer to
http://devart.com/forums/viewtopic.php?t=20834
AndreyR
Devart Team
 
Posts: 2919
Joined: Mon 07 Jul 2008 13:16


Return to dotConnect for MySQL