| Bug #69787 | MySQL Workbench times out on long query; command line (mysql) does not (linux) | ||
|---|---|---|---|
| Submitted: | 18 Jul 2013 23:37 | Modified: | 23 Jul 2013 18:42 |
| Reporter: | Rene Reitsma | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 5.2.47 rev 10398 | OS: | Linux (3.8.13-100.fc17.x86_64) |
| Assigned to: | CPU Architecture: | Any | |
[18 Jul 2013 23:43]
Todd Farmer
Hi Rene, thanks for your bug report. Have you tried increasing the "DBMS connection keep-alive interval" or "DBMS connection read time out" - both of which default to 600 seconds - in the SQL Editor preferences?
[19 Jul 2013 0:36]
MySQL Verification Team
Changing to Need Feedback for Todd's questions.
[19 Jul 2013 0:44]
Rene Reitsma
Aha!!! That would explain it. Thanks for figuring this out. I guess it's not a bug at all then. RR
[19 Jul 2013 19:57]
Rene Reitsma
Since the 600.0 seconds timeout constraint is set by MySQL Workbench itself, perhaps it might be a good idea to communicate this as part of the timeout error message. Something like: "command/query timed out after 600.0 seconds (to set timeout limit see...)" (communicating a possible/likely solution in the error message could save semi-ignorant users such as myself a lot of problem-solving time). RR
[23 Jul 2013 18:42]
MySQL Verification Team
Thank you for the feedback.
Description: A nasty, long query which I run in MySQL Workbench consistently times out ("disconnected") after "600.0 seconds".(or so MySQL Workbench claims). The exact same query completes fine (although it takes a long time) in the mysql shell running on the command line. How to repeat: NA Suggested fix: ??