Bug #296 mysqld-max binary does not fully shutdown
Submitted: 16 Apr 2003 6:14 Modified: 29 May 2003 10:30
Reporter: Jared Reeve Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:4.1 OS:Microsoft Windows (Windows 2000)
Assigned to: Bugs System CPU Architecture:Any

[16 Apr 2003 6:14] Jared Reeve
Description:
I started the mysqld-max as such:

> C:\mysql4.1\bin>mysqld-max -uroot --console
> 030416  8:10:20  InnoDB: Started
> mysqld-max: ready for connections.
> Version: '4.1.0-alpha-max'  socket: ''  port: 3306

I then initiated the shutdown as such:
> C:\mysql4.1\bin>mysqladmin -uroot shutdown  

> 030416  8:10:27  mysqld-max: Normal shutdown
> 
> 030416  8:10:28  InnoDB: Starting shutdown...
> 030416  8:10:30  InnoDB: Shutdown completed
> 030416  8:10:30  mysqld-max: Shutdown Complete

The command prompt remains hung.  Then I have to go kill the process from the task manager.

How to repeat:
1) Start the server
    "mysqld-max -uroot --console"
2) Shutdown the server
    "mysqladmin -uroot shutdown"

Suggested fix:
Complete the shutdown process.
[16 Apr 2003 6:28] Miguel Solorzano
Thanks for the report. This was already detected and
will fixed in the next release.
[17 Apr 2003 3:19] Vasily Kishkin
This problem exists if I do "net stop mysql". Problem with system libriary of visual C (in file thread.c and in function _endthread ()).
[6 May 2003 6:14] [ name withheld ]
The problem also occurs for me when using mysqld.  It can be started from the command prompt, or as a service, and it never shuts down cleanly. (And yes, I am using "mysqladmin -uroot shutdown" to shut the service down.)  As a service, it can never be stopped, as the Windows Task cannot be killed either, leaving a Zombie process that is neither started nor stopped.
[29 May 2003 10:30] Vasily Kishkin
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at 
    http://www.mysql.com/doc/en/Installing_source_tree.html

Problems was fixed. It was happend if mysqld was built with option shared memory.