Bug #397 | mysql.exe uses persistent connections which leads to 'too many connections' | ||
---|---|---|---|
Submitted: | 8 May 2003 5:13 | Modified: | 22 Dec 2003 10:20 |
Reporter: | Thomas Salvisberg | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 4.0.10-gamma-nt | OS: | Windows (Windows 2000 SP3) |
Assigned to: | CPU Architecture: | Any |
[8 May 2003 5:13]
Thomas Salvisberg
[14 May 2003 12:41]
Vasily Kishkin
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL. I tried to test it, but I could't find that connections was still open. I tested this by way....connecting, looking at connection count, disconnecting, look at connection count. Count of connections I checked by executing 'mysqladmin status' repeatadly.
[22 Dec 2003 10:10]
Moreno Gentili
I too have to report this same bug BUT on MySQL version 4.1.0-alpha-max-nt on WindowsXP prof. Please, test it with that setup. The problem is that the wait_timeout variable is ignored and sleeping threads are never killed.
[22 Dec 2003 10:20]
MySQL Verification Team
This bug was thoroughly fixed in the versions 4.0.17 and 4.1.2 Please test the first one from the tarball. You can test a second one from our BK repository.
[22 Apr 2005 15:11]
jair enrique gonzalez barragan
espero que me puedad dar infromacion de como utilizar mysql+