Default Command Timeout

Default Command Timeout

Postby noah » Wed 16 Feb 2011 03:12

We're seeing the following exception:
Devart.Data.MySql.MySqlException: Lost connection to MySQL server during query ---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.


Is this the same as a command timeout?

Additionally, we would like to increase the Default Command Timeout on our production servers to try to track this down. We've set the "default command timeout=90" inside our connection string in our app's .config file but it's still timing out at 30 seconds (the default). We're using Entity Framework 4.

Please advise!
noah
 
Posts: 3
Joined: Fri 25 Jun 2010 15:21

Postby Shalex » Wed 16 Feb 2011 10:52

Please try using the latest version of dotConnect for MySQL (6.10.103). If the problem persists with the newest build as well, post here your call stack.
Shalex
Devart Team
 
Posts: 7475
Joined: Thu 14 Aug 2008 12:44


Return to dotConnect for MySQL