Bug #15502 | TCP port > 32K shows 0 also unable to set TCP port > 62K | ||
---|---|---|---|
Submitted: | 5 Dec 2005 22:12 | Modified: | 7 Aug 2006 14:19 |
Reporter: | James Goodfellow | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 5 | OS: | Windows (Windows XP) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
Tags: | Server Configuration |
[5 Dec 2005 22:12]
James Goodfellow
[7 Dec 2005 18:54]
MySQL Verification Team
Thank you for the bug report. Also it fails to connect with a port > 62222 with an error message it isn't a valid integer value: C:\mysql5016>bin\mysql --defaults-file=c:\mysql5016\s5016.ini -uroot -p --prompt="win5016>" Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 5.0.16-nt-max Type 'help;' or '\h' for help. Type '\c' to clear the buffer. win5016>show variables like "port"; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | port | 62222 | +---------------+-------+ 1 row in set (0.00 sec) win5016>
[7 Dec 2005 20:03]
James Goodfellow
Using port 62222, I have connedted successfully with MYSQL admin v 1.1.5 under windows XP on multiple PCs on two different networks. The port number is displayed correctly in the port In addition, MYSQL Admin shows correctly(62222) in the Port display on the login screen(the one with Server Host, Port, Username and Password.) and the Server information screen. Also the MYSQL Server Instance Configuration Wizard 1.0.5 accepts 62222 and displays it correctly. I have not used the commandline feature. PHPmyadmin works with port 62222. Also the MYSQL query Browser. The only point of failure I see is that the port cannot be displayed or set in the admin program when it is >32K Also TCP ports are an unsigned integer so they are a valid unsigned 2 byte integer. yours Jim
[7 Aug 2006 14:19]
Michael G. Zinner
All spin control are limited to 32k. Therefor the spins have now been removed. This is now fixed in the source repository and will be included in the next release.