Bug #3702 MysqlCC not making interactive connections
Submitted: 10 May 2004 17:09 Modified: 1 Jun 2004 0:42
Reporter: Shaun Thomas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQLCC Severity:S3 (Non-critical)
Version:0.9.4-beta OS:Windows (Windows XP)
Assigned to: Jorge del Conde CPU Architecture:Any

[10 May 2004 17:09] Shaun Thomas
Description:
We were having trouble with mysqlcc frequently reporting "Error 2013: Lost connection to MYSQL server during query." if we didn't send a query or check a table every few seconds.  After checking the different timeout options, we noticed that our interactive_timeout was 8 hours, but wait_timeout was 60 seconds.  Since we don't want automated systems to hang up on the server for long periods of time, a wait_timeout of 60 seconds is what we wanted.

Either the server is treating interactive connetions like regular connections, or MysqlCC isn't telling mysql it wants an interactive connection.  I doubt the first, since I've left regular mysql console connections unattended for hours without this issue.

How to repeat:
1.) Set wait_timeout to a low number. 
2.) Make a connection to mysql server with MysqlCC.
3.) Wait longer than time set in step 1.
4.) Issue query.

This appears to affect both MysqlCC and the new Mysql Administrator.

Suggested fix:
make sure administrative tools make interactive connections to mysql.
[1 Jun 2004 0:42] Jorge del Conde
Hi!

MySQLCC has been discontinued and will not be developed nor maintained anymore with the exception of Critical bugs.

In the near future we will release the substitute of MySQLCC called MySQL Query Browser.