Bug #28629 | Query Execute Thread cannot connect to MySQL | ||
---|---|---|---|
Submitted: | 23 May 2007 17:59 | Modified: | 23 Jun 2007 20:04 |
Reporter: | Joe Hinder | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.2.11 | OS: | Windows (XP) |
Assigned to: | CPU Architecture: | Any |
[23 May 2007 17:59]
Joe Hinder
[23 May 2007 19:25]
Valeriy Kravchuk
Please, try to repeat with a newer version, 1.2.12, and inform about the results.
[23 May 2007 19:46]
Joe Hinder
Thanks for the quick response. Some more information for you: I tried to connect to the same database server on a different PC and got a message that said max_user_connections had been reached. So, I stopped and restarted my database and everything's ok again. Now, I don't know if "Query Execute Thread cannot connect to MySQL" was a symptom or a cause, but I do know that stopping and restarting the server cleaned up my user connections. I need to watch the server for while to see if the Query Browser was holding connections open or if there is another application that is causing this.
[23 May 2007 20:04]
Valeriy Kravchuk
Please, inform about any results of your check.
[23 Jun 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[28 Nov 2008 11:17]
andrey bogapov
if you used named pipe, you mast connect from stored connection ( Advanced Parameters- NAMED_PIPE Yes SOCKET_PACH yousocket)