Bug #79447 | Lost Connection is Very Frequent | ||
---|---|---|---|
Submitted: | 30 Nov 2015 2:03 | Modified: | 25 Nov 2016 10:13 |
Reporter: | Louis Gualtieri Jr | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 6.3.5/6.3.6 | OS: | Windows (Microsoft Windows 10 Pro) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Connections, timeout, WBBugReporter |
[30 Nov 2015 2:03]
Louis Gualtieri Jr
[30 Nov 2015 2:44]
Louis Gualtieri Jr
To add to this: I can confirm rolling back to version 6.1 solves the problem for me.
[30 Nov 2015 12:45]
Adrian Leishman
Same on Debian Jessie 64bit I get enough time to run 1 query and then the connection is lost. This does not appear to happen on "localhost" connections, just remote.
[9 Dec 2015 23:07]
Nathan Christiansen
I observed this with "MySQL Workbench Community (GPL) for Windows version 6.3.5 CE build 201 (64 bit)" on a Windows 8.1 System. It was a 60 second timeout. That was the same as the SQL Editor setting "DBMS connection time out". I adjusted the setting "DBMS connection keep-alive interval" to 10 seconds. I upped the setting "DBMS connection time out" to 600 seconds. And the the connection was still closed at around 60 seconds. I was able to keep the connection alive for several minutes by manually running queries before the 60 second idle mark. Our Server times out the connections in 180 seconds of idle. (The DB is a Galera Clustered, MariaDB 10.0 over three servers.) The prior release 6.3.4 did a good job in auto-reconnecting even after the connection was hours idle.
[20 Dec 2015 19:11]
MySQL Verification Team
http://bugs.mysql.com/bug.php?id=79715 marked as duplicate of this one.
[20 Dec 2015 19:14]
MySQL Verification Team
http://bugs.mysql.com/bug.php?id=79653 marked as duplicate of this one.
[24 Oct 2016 21:44]
MySQL Verification Team
Please try version 6.3.8. Thanks.
[25 Nov 2016 1:00]
Bugs System
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".
[25 Nov 2016 10:03]
Crowle Brent
Tested 6.3.8 and the issue is resolved for me
[25 Nov 2016 10:13]
MySQL Verification Team
Thank you for the feedback.