Bug #2720 Max Connections Reported Incorrectly
Submitted: 11 Feb 2004 21:28 Modified: 19 Feb 2004 11:21
Reporter: Mike Zimmerman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.1a OS:Windows (Win32)
Assigned to: Michael G. Zinner CPU Architecture:Any

[11 Feb 2004 21:28] Mike Zimmerman
Description:
Max connections in connection health is reported as 100, regardless of the configured maxium.

How to repeat:
Set max connections above 100 and look at the connection health page.
[13 Feb 2004 12:56] [ name withheld ]
I think what is happening is the max connections are being read from the actual max connections and not the max connections being set by the variable. I have max connections set at several thousand but the max connections shows 114 with no one connected other than some simple scripts. When I take the actual connections up to about 1000 the max connections changes to that number. Since the actual connections are what is being set as max then it also reports usage at 100 percent when my scripts fire off and I haven't had more connections. If I make 1000 actual connections, and the max then reads that number, the usage gets reported at 10 percent for my scripts.
[17 Feb 2004 3:47] Michael G. Zinner
Thanks for your reports.

This bug has now been fixed. The fix will be available in release 1.0.2a.