Bug #49252 Process ID
Submitted: 1 Dec 2009 8:59 Modified: 11 Dec 2009 11:16
Reporter: Daniel Seif Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.2.12 OS:Windows (XP)
Assigned to: CPU Architecture:Any

[1 Dec 2009 8:59] Daniel Seif
Description:
When the PID of a mysql connection process is too large, killing them using the "kill thread" button in the View "Threads" is not possible. It gets blocked with the error message "<PID> is not a valid integer value"

How to repeat:
Let a MySQL server run for severl months and query it with millions of queries per day (simply: let the PID count get high enough). Then select an open connection in the Administrator and try to kill it.

Suggested fix:
Don't use integer values for PIDs in the Administrator, but rather use a bigint or any other datatype which can handle large numbers (or strings representing large numbers)
[8 Dec 2009 13:18] MySQL Verification Team
Thank you for the bug report. Are you tried to do the same using the mysql.exe client tool?. Thanks in advance.
[8 Dec 2009 13:37] Daniel Seif
The mysql.exe client doesn't show this behaviour. It seems to be an error in the GUI itself
[11 Dec 2009 11:16] Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench and won't fix this anymore in MySQL Administrator.

Lots of parts of Administrator are already implemented in MySQL Workbench 5.2.

We made a deeper source code analysis here from MySQL Workbench to be sure that we not by accident made same error here as in MySQL Administrator.

According to our analysis it should not happen in Workbench.

More informations about Workbench you will find here:

http://dev.mysql.com/workbench/