Bug #58560 preferences for keep-alive interval and status update interval have no effect
Submitted: 29 Nov 2010 13:33 Modified: 25 Apr 2011 2:05
Reporter: Martin Leboeuf Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.30 CE, 5.2.31 OS:Windows (XP pro)
Assigned to: CPU Architecture:Any
Tags: interval, keep-alive, preferences, STATUS, UPDATE

[29 Nov 2010 13:33] Martin Leboeuf 
Description:
The "Progress status update interval (in milliseconds)" and "DBMS connection keep-alive interval (in seconds)" on the "SQL Editor" tab of the "Edit->Preferences" menu of MySQL Workbench 5.2.30 CE seem to have no effect. I just upgraded to that version of MySQL Workbench, and modified those parameters, but it seems the default value are still being used: I am running a lengthy query and 1) the admin page still gets refreshed every 5 seconds although I changed the parameter to 10 seconds and 2) I get a two errors messages with Error code 2013 and 2006, respectively, on the SQL Editor page after 600 seconds, although I changed the keep-alive parameter to 6000 seconds.

Is this really a bug or am I doing something wrong ?

How to repeat:
1) modifiy the two aforementionned parameters
2) run a query that takes longer than the default 600 seconds to run
3) monitor it on the admin page
[13 Dec 2010 15:01] MySQL Verification Team 
It was against a local or remote server?. Are you tried the new version 5.2.31?. Thanks in advance.
[13 Dec 2010 18:06] Martin Leboeuf 
It is against a remote server. I just updated to 5.2.31 and I get the same behavior i.e. changing the parameters has no effect.
[25 Jan 2011 17:00] Samir Abboushi 
I have the same problem on Vista 64 SP2: Error code 2013 and 2006 after 600 seconds even after changing the dbms connection keep-alive interval to 28800.
[27 Jan 2011 20:18] Sveta Smirnova 
Thank you for the report.

Verified as described.
[29 Jan 2011 20:53] danny wold 
I have the same problem: 600 seconds, no init file changes or preference editing helps. I'm dismayed this both made it into the release and was not addressed for two months.
[25 Apr 2011 2:05] Alfredo Kojima 
The status update interval has no effect on the Admin module, it is used for status update of the SQL editor itself.

Similarly, the keep-alive setting is for maintaining a connection alive when there's nothing running on it. For long running queries, the option would be another one, in that case there already is a feature request for it in bug #60103