MySQL Bugs: #45123: MySQL Workbench crashes on timeout session

Bug #45123	MySQL Workbench crashes on timeout session
Submitted:	27 May 2009 9:33	Modified:	28 Aug 2009 8:23
Reporter:	Giuseppe Maxia	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.1	OS:	MacOS (10.5.6)
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any
Tags:	CHECKED, crash, mac, osx, timeout, workbench

Description:
I opened Workbench and I created a table.
Several hours later, with WB still open, I tried to insert fields in that table, and I got a message saying that the MySQL Server had gone away.
Figuring out that there had been a timeout, I connected once more, and WB crashed a few seconds later.

See the track file attached

How to repeat:
see above

Crash was fixed.

Added sending of dummy requests to keep DBMS connection alive, Interval between `keep alive` requests is determined by `DbSqlEditor:KeepAliveInterval` global parameter (see /wb/options/options branch of GRT Tree), `0` value for this parameter means no `keep alive` requests.

Added OPT_RECONNECT option for MySQL DBMS connection, which allows to restore connection automatically (when it's possible) using MySQL Connector facilities. User needs to repeat his action when he encounters `server has gone away` error message to try to restore connection.

crash was fixed for release 5.2.2.

An entry was added to the 5.2.2 changelog:

If MySQL Workbench gave the message that the MySQL Server was no longer available (because of timeout due to inactivity) then MySQL Workbench crashed when the user tried to reconnect.