MySQL Bugs: #6599: MySQL Administrator crashes when connecting through named pipes

Bug #6599	MySQL Administrator crashes when connecting through named pipes
Submitted:	12 Nov 2004 16:50	Modified:	29 Nov 2006 13:41
Reporter:	Charles Canato	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.14	OS:	Windows (Win2K Adv Server)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
I've configured my server to accept only named pipes connections. Works wonderfully with the command-line utilities, but MySQL Administrator just crashes when I force a named pipes connection.

How to repeat:
Fill the Hostname field with a ".", indicating a named pipes connection. It doesn't matter what value you fill in the port field, it apparently ignores it (which is expected) - but you must fill one to be able to try to connect.

After you press OK, the MySQL Administrator crashes. If you monitor it with the Task Manager, you'll see memory increasing a bit during some time (normally, your mouse pointer will turn to "hourglass" mode also", DRWTSN32.EXE coming into action, and then, after some seconds, both of them just disappearing.

The server isn't affected in any way, but through the error log (warnings enabled) I can see a connection has been made:
------
041112 14:19:03 [Warning] Aborted connection 1 to db: 'unconnected' user: 'root' host: `localhost' (Got an error reading communication packets)
------

I've tested with some different MY.INI settings in [mysqld] section, but all these scenarios generate the crash:
* skip_networking ON or OFF (my default is OFF)
* port= given a value or not present at all (my default: not defined)
* disable_host_names ON or OFF (my default: not defined)

The problem DOES NOT HAPPEN if the server is stopped or named pipes aren't enabled, which seems obvious and makes me think it's really an "after the connection" problem.

This bug has been open for a long time (actually it is our longest unfinished bug in the GUI category). The reason is that its priority as well as severity is not that high, simply because named pipes aren't used much. Even the server comes with disabled named pipes by default. The current MA version does not allow to connect to a server like "." anyway (it always tries to resolve that name and does not recognize it as command to use named pipes, which obviously fails with names like ".").

Given this situation I'll close this bug and mark as "won't fix" because we will likely never allow named pipe connections with the current MA version (or QB for that matter). If there is enough interest we will consider including that ability again in the next major version. For now, however, consider named pipe connections as non existant. I removed the appropriate option from the connection dialog.

Mike

Update: connections through named pipes are supported for quite some time now.