Skip to content
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

Server hangs for 60/120 seconds if client exits during database encryption key transfer callback [CORE5815] #6077

Closed
firebird-automations opened this issue May 4, 2018 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

If client for some reason does not reply to the callback request for dbcrypt key (for example - segfault in callbak code) server waits for reply packet for 60 sec and may be 60 more sec for one more callback. During this time server can process other users' requests except attach/detach database and can't exit/restart normally.

Commits: 845fb38 6863601

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Alexander,

I think you meant to write "During this time server can *not* process other...", correct?

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

Fix Version: 3.0.4 [ 10863 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

No.
During this time server *can* process other users' requests but not all - attach and detach are impossible. Existing attachments continue work normally. There is mutex locked that is in use during attach and detach.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Cannot be tested

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment