Bug #54098 Unable to close Admin config instance tabbed window with running Mysql server
Submitted: 31 May 2010 9:00 Modified: 17 Jul 2010 14:04
Reporter: Koos van Klojum Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.22 OS:Windows (XP Pro SP3)
Assigned to: CPU Architecture:Any
Tags: Apache 2.2.15, mysql 5.1.45, Zend Server CE

[31 May 2010 9:00] Koos van Klojum
Description:
Workbench application produces an error when closing an Admin config instance tabwindow, when the MySQL database service is running beforehand. This also happens with a second instance of that same Admin config instance.

Workbench application produces NO error when closing an Admin config instance tabwindow, when the MySQL database service is NOT running beforehand. This also happens with a second instance of that same Admin config instance.

Workbench application produces an error when closing an Admin config instance tabwindow, when the MySQL database service is NOT running beforehand and IS started during the Workbench application. This also happens with a second instance of that same Admin config instance.

How to repeat:
1ST SITUATION
Opening a server instance from the Home screen of MySQL Workbench via doubleclicking opens a tab window of that instance.

I have one instance, with status:
2010-05-31 10:25:21 - Checked server status: Server is running.
2010-05-31 10:25:22 - Server is running
which is correct.

Clicking on the X of the window tab results in an WB application error messagebox:
"Error"
<White cross in red circle>  Unhandled exception [Errno 22] invalid argument

Closing that messagebox will not do anything further, and the tab window does not close. Several clicks on the X will result in the same behavior as above.

2ND SITUATION
-------------
If I have no running MySQL server:
- manually stopped the database engine service)
- I start the Workbench application
- Doubleclick the Admin config instance (it says
  2010-05-31 10:34:13 - Checked server status: Server is stopped.
  2010-05-31 10:34:14 - Server is stopped
  (which is correct)
- Now I can close the Admin config tab window with no problem. No application error, and the tab is closed like it is supposed to.

3RD SITUATION
-------------
- First manually stop the database engine service)
- I start the Workbench application
- Doubleclick the Admin config instance (it says
  2010-05-31 10:34:13 - Checked server status: Server is stopped.
  2010-05-31 10:34:14 - Server is stopped
  (which is correct)
- I restart the MySQL service manually
- Now the WB application error #22 arises again, and the tabwindow cannot be closed...

Outcome is the same every time afer a restart of the WB application, and also even reboot of the computer.

Results are consistent, with a running AND non-running MySQL engine service.

Using:
XP Pro SP3

Zend Server Community Edition
(ZendServer-CE-php-5.3.2-5.0.1-Windows_x86.exe)

Included items:
* PHP 5.2 version updated to 5.2.13 - Specific release information is available
  at http://www.php.net/releases/5_2_13.php

* PHP 5.3 version updated to 5.3.2 - Specific release information is available
  at http://www.php.net/releases/5_3_2.php

* Zend Framework updated to version 1.10.3 - Specific release information is 
  available at http://framework.zend.com/changelog/1.10.3

* New versions of the following 3rd party modules:
  - MySQL 5.1.45
  - OpenSSL 0.9.8n
  - LibCURL 7.20.0
  - Apache 2.2.15
  - lighttpd 1.4.26

Suggested fix:
None, sorry... Hope you find this bugger.
[2 Jun 2010 9:08] Susanne Ebrecht
How much MySQL instances are running on your machine?
On which OS is/are the server running?
Is/are the server local or remote?
[2 Jun 2010 9:22] Koos van Klojum
>> How much MySQL instances are running on your machine?
>> On which OS is/are the server running?
>> Is/are the server local or remote?

There are 2 separate MySQL instances running:
- First one (v5.1.45) is running local on the XP Pro SP3 laptop (Core2Duo 1.6Mhz Centrino)
- Second one (5.1.34) is running external on a Synology DS209+ NAS, running a Linux variant.

Any combination of those two is producing the same behavior as described.
[2 Jun 2010 12:30] MySQL Verification Team
I couldn't repeat with a local server on Windows Vista 64-bit.
[5 Jun 2010 2:39] MySQL Verification Team
Could you please try version 5.2.22.Thanks in advance.
[6 Jun 2010 12:52] Koos van Klojum
Okay.. it seems that my laptop is acting up somehow. Although it has over 100 tools & applications installed that do behave normally, MySQL Workbench is only the second program that is responding weirdly.

I now have my other, second PC (Intel E8200 workstation, also WinXPSP3, WB 5.2.21), that does -not- show the abnormalities when closing the Admin Instance tabwindow... (*sigh*).

Strange(r) behavior: I upgraded the problem laptop to 5.2.22. The very first time WB started, it seemed to behave well. Even the Server start/top button in the tabwindow worked flawlessly. Then... tried to close the Admin instance tabwindow, and got the dreaded Error #22 again. After that, also the Server start/stop button stopped reacting: it attempts to start/stop the MySQL server, but the status remains the same: stopped=>stopped, and running=>running. Even after closing and restarting the WB application. :-\

In which location does Workbench store its settings like current & previous opened files? Is it in some .INI-file or in the registry? (in case of cleaning _all_ things related to re-installing WB)

I want to try & transfer those settings to the workstation PC (that doesn't have those problems I'm experiencing on the laptop).
[17 Jun 2010 14:04] Mike Lischke
The settings for WB are stored in the local user settings. For XP this is usually C:/Documents and Settings/<user>/Application Data/MySQL/Workbench. Please also try with our new release which will come soon. Thank you.
[17 Jul 2010 23: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".