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

A regular deadlock may not be detected by the lock manager under some conditions, thus resulting in a hang [CORE2640] #1127

Closed
firebird-automations opened this issue Sep 25, 2009 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

Is related to CORE2000

It seems that the fix for CORE2000 was incomplete and may cause a hang if the just granted request doesn't have an assigned AST routine. In this case, it happened for transaction locks: transactions A and B wait for each others uncommitted versions and no deadlock is reported after the default interval of 10 seconds.

Commits: 35be85e 4d18b2e bc7f2e6

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is related to CORE2000 [ CORE2000 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10362 ]

Fix Version: 2.1.4 [ 10361 ]

Fix Version: 2.0.6 [ 10303 ]

@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