Bug #79467 keep-alive timeout is no longer working
Submitted: 1 Dec 2015 1:24 Modified: 1 Feb 2016 21:51
Reporter: jean cerien Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.5 build 201 CE 64bits OS:Ubuntu (14.04 - mint 17.2)
Assigned to: CPU Architecture:Any
Tags: keep-alive

[1 Dec 2015 1:24] jean cerien 
Description:
the keep-alive timeout is no longer working (pref/sql editor/ dbms connection keep-alive interval).
No traffic is observed when monitoring packets on the mysql server host, and the session dies (in my case) systematically within 5 minutes of last activity.

Regressing to 6.3.4 0 build 828 64bits, (dpkg -r then -i) with the same data in ~/.mysql/workbench restores proper functionning

see also: http://forums.mysql.com/read.php?152,637676,637676#msg-637676

How to repeat:

On Ubuntu 14.04/Mint 17.2

- Install 6.3.5 build 201 CE 64bits
- have a network element to the sever closing the connection
- loose your session, and then, kill mysql-workbench
[1 Dec 2015 1:27] jean cerien 
from wb_options
      <value type="int" key="DbSqlEditor:ConnectionTimeOut">60</value>
      <value type="int" key="DbSqlEditor:ReadTimeOut">600</value>
      <value type="int" key="Fabric:ConnectionTimeOut">60</value>
      <value type="int" key="sshtimeout">10</value>

      <value type="int" key="sshkeepalive">30</value>

connection is done NOT via ssh
[2 Dec 2015 7:59] László Somogyi 
Same for me (Windows 7 x64). SSH keepalive works, but when using simple tcp connection, then that rdbms keepalive doesn't (worked on 6.3.4). So always mysql gone away or just getting back result as read-only or crash.

Sadly i have a db which has some tables i cannot query with an ssh connection since 6.3.5, but i can with tcp :D But the tcp conn always dies cause no keepalive, so very sad situation on 6.3.5 :P
[1 Feb 2016 21:51] MySQL Verification Team 
Thank you for the bug report. Duplicate of http://bugs.mysql.com/bug.php?id=80225.