MySQL Bugs: #29210: MySQL timeout

Bug #29210	MySQL timeout
Submitted:	19 Jun 2007 13:06	Modified:	20 Jun 2007 20:50
Reporter:	Marc Sàbat	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / NET	Severity:	S3 (Non-critical)
Version:	5.0.5	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	debug, Release, timeout

Description:
Hello,

Recently we discovered (the hard way) that there is a small difference between Release and Debug.

At line 376 on file command.cs there is this piece of code:
#if !DEBUG
                if (connection.driver.Version.isAtLeast(5, 0, 0) &&
                     commandTimeout > 0)
                {
                    TimerCallback timerDelegate =
                         new TimerCallback(TimeoutExpired);
                    t = new Timer(timerDelegate, this, this.CommandTimeout * 1000, Timeout.Infinite);
                }
#endif

Everything worked fine when debugging (i.e. launching the app from VS2005). It hang when executing on release mode.

I really don't have the time to generate a simple test case but our application was just performing a SELECT on a table.

I wonder if this difference is really expected between release and debug modes.

Thanks

How to repeat:
I'm not sure yet. Perhaps is because we opened two connections pointing to the same database.

Anyway, the question is, does this code need to be different between debug and release modes ?

Hi Marc and thanks for your report. So far, I can tell that difference is there in latest sources too. Will need to consult...

Marc, I forgot that timing-out was bothering me while debugging old versions... In any case, as c/NET team leader explained to me, this is intended behavior in debug mode.