Bug #22468 MySQL Administrator randomly looses connection to MySQL DB
Submitted: 19 Sep 2006 8:26 Modified: 1 Dec 2006 8:32
Reporter: Jacques Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.2 OS:Windows (Windows XP)
Assigned to: Mike Lischke CPU Architecture:Any

[19 Sep 2006 8:26] Jacques
Description:
MySQL Administrator randomly looses it's connection to a MySQL 5.1.11 server.

How to repeat:
Work with MySQL Administrator and it will randomly loose it's connection to the database server.

Suggested fix:
Make MySQL Administrator persistently reconnect to the MySQL database server when it's connection goes away.
[19 Sep 2006 11:33] Arnoud Witt
MySQL Administrator does not automatically reconnect if the server has timed out.
Even if you have the Health section open for a while, then switching to Server Connections and then click on Refresh it comes with the message "Lost connection to MySQL server during query", which is common, when a connection has not been used for a while.
The Health section uses a different connection next to the Server Connections section. Why? One connection to the server seems to me to be enough. MySQL Administrator should keep the connection alive and automatically reconnect when the connection failed.

To add to this, when Selecting Reconnect from the File drop down menu, the Connection dialog box is opened behind other windows and the current Administrator window closes.
[21 Sep 2006 8:00] Sveta Smirnova
Thank you for the report.

Could you please try using current MySQL GUI Tools 5.0-r3 accessible from http://dev.mysql.com/downloads/gui-tools/5.0.html?
[29 Sep 2006 12:07] Jacques
Hi Sveta,

I'll let you know if I notice anything else.  I've downloaded the latest version and I've installed it.

Regards
--jm
[29 Sep 2006 12:09] Jacques
Hi Sveta,

If I kill the one process via KILL XXXX; and it does not persistently reconnect.

Regards
--jm
[3 Oct 2006 9:29] Sveta Smirnova
Thank you for the report.

Verified as described in last comment: issue KILL pid; in mysql command line client or similar mysqladmin command. Note this issue is repeatable only if one tries to connect to remote host. On localhost MySQL Administrator reconnects to the server after some seconds.
[5 Oct 2006 11:53] Mike Lischke
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html
[20 Oct 2006 10:11] Jacques
Bug still exists in 1.2.4 rc which I've installed.
[24 Oct 2006 6:27] Mike Lischke
Killing the server process is something completely different than just losing the connection because of network problems. I wouldn't say that this situation is well described by saying MA loses connection randomly. So can you please be more specific? Do you expect that MA reconnects automatically even if the server has been complete restarted (which would be low prio feature request) or do you say it is still losing connection and not able to reconnect if you just let it alone for an hour or so (which would be a bug we have to investigate)?

If the latter then I have trouble to reproduce the problem. I have left an MA instance running for more than 12 hours (just the initial screen, no health section) and still could work with it after that time without the need to restart MA.
[24 Oct 2006 7:27] Jacques
For example I left a couple MySQL Administrator instances running over the weekend.  Only one of them was still connected when I got in to work yesterday morning.  All the MySQL servers I connect to are currently located on the same floor in the building.  SSH sessions also stay up except for external SSH connections which get reset every 24 hour due to the fact that our telecoms monopoly have a session time limit of 24 hours.
[27 Oct 2006 7:25] Mike Lischke
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html
[27 Oct 2006 7:27] Mike Lischke
I'm sorry. Accidentally, I closed the wrong bug report. I'll try to reproduce the problem, but have not much hope I can help, if I cannot reproduce it.
[27 Oct 2006 7:54] Jacques
Do you have some sort of debug build that writes to a debug.log what it is doing?
[30 Oct 2006 8:35] Mike Lischke
There is no separate log for the tasks that are executed. It's a lot of work to cover all relevant parts and queries are already logged by the server. Additionally, such a log would only help in very rare cases.

Please try the next release which should be available very soon and let us know if that works finally for you. I have left MA running over the weekend and could work with it after that without any problem. MA pings the server once in a second and that should keep the connection alive. I'm thinking of increasing this time to once in a minute or so if it works out well.
[1 Dec 2006 0: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".
[1 Dec 2006 8:32] Sveta Smirnova
Sorry for missing your comment.

It is not repeatable now.