Bug #82268 Mysql Workbench queries not working through odbc connection
Submitted: 18 Jul 2016 13:20 Modified: 20 Jul 2016 8:07
Reporter: Mark Harris Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.3.7 OS:Any
Assigned to: CPU Architecture:Any

[18 Jul 2016 13:20] Mark Harris
Description:
Mysql Workbench has a tendency to timeout sometimes when running a query. The error that comes up is "error code: 2013 Lost Connection to Mysql Server at 'waiting for initial communication packet".

I'm running very small queries on tables not larger than 40k of records, though it is through a odbc connection. Is there a workaround available for this issue or a way of identifying if it is a problem with my side of the connection or the other side through the odbc?

How to repeat:
Is completely random, however normally happens 5-10 minutes into using mysql workbench.
[18 Jul 2016 17:03] MySQL Verification Team
Thank you for the bug report. Please provide the exaclty version of WorkBench, The OS are you running and the MySQL server version you are connection to and a scree-shot when you are setting the ODBC connection. Thanks.
[19 Jul 2016 7:39] Mark Harris
I am using Mysql Workbench 6.3.7 and Windows 7 Professional 32-bit. I can send you a screenshot of the connection, however I will take out any username details for obvious security reasons.
[19 Jul 2016 7:42] Mark Harris
Screenshot of connection to odbc

Attachment: Issue with Mysql Workbench.png (image/png, text), 49.71 KiB.

[19 Jul 2016 11:45] MySQL Verification Team
Thank you for the details and screenshot.
I'm seeing this issue on Win7 with WB 6.3.7 with connection method "Standard TCP/IP over SSH".
[19 Jul 2016 11:46] MySQL Verification Team
Screenshot..

Attachment: 82268.png (image/png, text), 71.57 KiB.

[20 Jul 2016 8:07] Mark Harris
That's exactly the issue. Any suggestions on a workaround or is this a issue with Mysql Workbench that will need to be resolved?
[21 Jul 2016 8:10] MySQL Verification Team
Bug #82256 marked as duplicate of this