MySQL Bugs: #79904: Lost Connection to MySQL with Standard (TCP/IP) connection Method

Bug #79904	Lost Connection to MySQL with Standard (TCP/IP) connection Method
Submitted:	10 Jan 2016 4:41	Modified:	29 Feb 2016 16:34
Reporter:	Craig Doumouras	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.3.6	OS:	MacOS (Mac OS X (OS X 10.11.x El Capitan))
Assigned to:		CPU Architecture:	Any

Description:
If I run a query in Workbench, and receive a result, I am unable to run a new query unless I re-connect to the MySQL server manually.  I always get the following message:
'Error Code: 2013.  Lost connection to MySQL server'.   My connection method is a Standard (TCP/IP) connection.

My previous version of Workbench (6.3.3) did not have this issue.  It would reconnect automatically.

I must press the 'Reconnect to DBMS' button every time, and then make sure I run my query immediately the moment it connects.  If I wait more than (approximately) 5 seconds before executing a query, the server disappears again.

 

How to repeat:
Connect to a server, and run a query.  Wait 10 seconds or more, and try and run another query.  It happens every time, even when the MySQL server is on localhost.

Changing the MySQL Session variables in Workbench Preferences doesn't fix the problem.

Suggested fix:
1.  Keep connections alive (connections seem to disappear immediately)
2.  reconnect automatically when a query is run.

Which version of the MySQL server are you ran the queries?. Thanks.

I am able to reproduce this error on Windows 8.1 using Workbench 6.3.5.

I connect to a MariaDB 10.0 server.

This issue did not appear in Workbench 6.2, it was not until I upgraded to 6.3 that I started having this issue.

The connection timeout on my server is set to 2 minutes. If I wait for mote than 2 minutes between queries, I MUST use the Query..Reconnect To Server menu option.

Setting a keepalive does not keep the connection open. (Our server might not be set up to respond to keepalive requests.)

My suggested fix is that there be a preference to automatically reconnect to the server if the connection is lost.

MariaDB isn't supported.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".