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

Deadlock in classic server on linux [CORE1410] #1828

Closed
firebird-automations opened this issue Aug 9, 2007 · 7 comments
Closed

Deadlock in classic server on linux [CORE1410] #1828

firebird-automations opened this issue Aug 9, 2007 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Under heavy load classic server, actively working at the same time with events, gets locked.

That happens due to processing of lock manager and event signals in different order in different instances of fb_inet_server. One locked mutex for events and tries to lock mutex for lock manager, another locked mutex for lock manager and tries lo lock mutex for events. I.e. we have typical deadlock.

To avoid it we need to learn to inhibit signals not only from main code, but from AST's too.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12790 ] => Firebird [ 15332 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

This kind of deadlock happened due to not completely async signal safe code in AST/event handlers. Since 2.5 ASTs never run in event handlers, and the fact that this issue is gone currently confirmed by our testers.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: In Progress [ 3 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Cannot be tested

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