Description:
I'm using MySQL Administrator 1.0.21 on Windows XP alongside MySQL servers 4.0.24 (service name MySQL40, port 3306) and 4.1.12a (service name MySQL41, port 3307) (each has their own program and settings folders, let's say C:\mysql40 and C:\mysql41) with MySQL Query Browser 1.1.10. When I run Administrator normally from the start menu or the "MySQL Administrator" link on the MySQL System Tray Monitor and log in to the 4.0 server, when I go to either the server status, startup variables, or server logs page, those pages show the information for the correct (4.0) server, listing the settings folder in the startup variables page as being in C:\mysql40. However, when I log in to the 4.1 server by the same normal method and go to the server status, startup variable, or server logs pages, they display the information for the 4.0 server (the settings folder in the startup variables page is listed as being in C:\mysql40, not C:\mysql41). I can change the startup variables and view the 4.1 server status and logs from the direct links listed under the MySQL41 service in the System Tray Moniter (same for the 4.0 server and MySQL40 service), but Administrator itself will only show that information for the 4.0 server. This also occurs with MySQL Administrator 1.0.14.
Note: The part about the server logs, I haven't gone through to confirm. The other two I am certain about.
How to repeat:
Install both a MySQL 4.0 server and a 4.1 server (this also happened using 4.0.23 and 4.1.7) in that order, and assign the port 3306 to the 4.0 server and 3307 to the 4.1 server. Install MySQL Administrator and Query Browser (latest versions), and run MySQL Administrator, logging in to the 4.1 server. Verify that you are logged in to the 4.1 server, then go to the Server Status page; it should pause, then show the status of the 4.0 server. Go to the Startup Variables page; it should show the variables location as being in the 4.0 installation folder. Next, go to any other page, and it will either say you're disconnected from the server, or will show the correct information for the 4.1 server for that page.
Suggested fix:
This could have something to do with the server status/logs & startup variables pages using only the default port (3306) and not checking what port the user is logged in on when getting server info, so it only gets info for the server that is on the default port. This could also explain the pause mentioned in "How to repeat".
