Bug #1141 Losing connection to Database causes Mysqlcc to exit (crash)
Submitted: 26 Aug 2003 4:07 Modified: 27 Aug 2003 0:27
Reporter: Ronan O'Connor Email Updates:
Status: Closed Impact on me:
None 
Category:MySQLCC Severity:S1 (Critical)
Version:0.9.2 OS:Linux (Redhat 8)
Assigned to: CPU Architecture:Any

[26 Aug 2003 4:07] Ronan O'Connor 
Description:
If connection to database is lost(perhaps because mysqld dies, or bad or missing internet connection), Control Center exits (crashes). When mysqlcc is rerun, it notes that the previous instance died due to a "Segmentation Fault".

How to repeat:
Open Mysqlcc and connect to a host running the mysqld. In the MySQL Servers pane, Double click a Database for this host (say mysql), double click the "Tables". Single click one of the tables (say user). Stop the mysqld. Double click one of the tables from the stopped mysqld (say user or host). Control Center exits (often the table query window opens for an instant).

Suggested fix:
If no connection to mysqld is found, Control Center should return host to the "unconnected state" in the MySQL Server pane.
[26 Aug 2003 18:59] Steve Brenneis 
Occurs consistently on RedHat 8 and RedHat 9 when connected to remote host via VPN tunnel.

Connection does not need to be completely broken. Occurs on slow or delayed connections as well.
[27 Aug 2003 0:27] Jorge del Conde 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html