Bug #42952 | Can't logon | ||
---|---|---|---|
Submitted: | 18 Feb 2009 2:17 | Modified: | 23 Feb 2009 11:28 |
Reporter: | Jared S (Silver Quality Contributor) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.2.16 | OS: | Windows (NT X.X) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | deniel, logon, qc |
[18 Feb 2009 2:17]
Jared S
[18 Feb 2009 12:54]
Valeriy Kravchuk
Thank you for the bug report. Verified just as described.
[23 Feb 2009 11:28]
Mike Lischke
I'm sorry, but we cannot fix that. What happens is that the connection is created in a background thread and this thread is simply killed when the user cancels the connection request before the usual timeout kicks in. However, this seems to leave a lock in place or similar, so every following attempt, even from a new thread, blocks. The work around is to wait for the timeout to kick in (you can set a very low value for that if you frequently have non-working connections) and then try again with another connection/host. This would then work as usual. Another option is to just cancel the connection dialog entirely, which closes MA, and try again.