New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SuperServer can't shutdown immediately after shutdown request after failed login attempt [CORE1421] #1839
Comments
Modified by: @AlexPeshkoffFix Version: 2.1 Beta 2 [ 10190 ] => |
Commented by: @AlexPeshkoff To be backported to 2.0 & 2.1. |
Modified by: @AlexPeshkoffFix Version: 2.5 Alpha 1 [ 10224 ] |
Modified by: @pcisarWorkflow: jira [ 12861 ] => Firebird [ 14663 ] |
Commented by: @AlexPeshkoff also should be backported to 2.1.1 |
Modified by: @AlexPeshkoffFix Version: 2.0.4 [ 10211 ] |
Commented by: @AlexPeshkoff Selected better place to delay thread which detected massive bad logins. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1.1 [ 10223 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: @hvlad
Start SuperServer, attach to any database with wrong password, stop server.
Here we have a delay before server shutdown.
Commits: 50af4e6 86367ce a862d1e d7f4bfb ba5b321
The text was updated successfully, but these errors were encountered: