Bug #57630 error code 2013 and 2006 server gone away
Submitted: 21 Oct 2010 14:02 Modified: 21 Oct 2010 14:36
Reporter: Gustav Gans Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.29 OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: lost connection server away

[21 Oct 2010 14:02] Gustav Gans 
Description:
This follows up http://bugs.mysql.com/bug.php?id=55419 as I cannot reopen it nor can I do any posting in the original forum thread.

I switched today from Mysql Query Browser 1.2.17 to the named Workbench version using the sql editor feature. A longer query (> 30 secs) does not run as it stops at exactly the 30 seconds border. I rechecked with the MysqlQueryBrowser and the query runs there perfectly. I searched quite a lot to find a solution to the problem, but could not find any yet. Are there any hidden settings with the Workbench. A limitation to 30 seconds is of course not acceptable.

How to repeat:
Hard to tell. Run a long query and try to hit that border. Try longer query, if still failing to reproduce. The referenced bug report had a comment implying a TCP timeout settings. A network feature. Perhaps anyone else knows more about this. I am clueless.
[21 Oct 2010 14:36] Valeriy Kravchuk 
This is likely a duplicate of bug #57449.