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.

Sign up for GitHub

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

Jump to bottom

Lock manager crash (invalid lock ID) under concurrent DDL load [CORE1965] #2403

Closed
firebird-automations opened this issue Jun 26, 2008 · 8 comments
Closed

Lock manager crash (invalid lock ID) under concurrent DDL load [CORE1965] #2403

firebird-automations opened this issue Jun 26, 2008 · 8 comments
Assignees
@dyemanov
Labels
affect-version: 2.5 Alpha 1 affect-version: 2.5 Initial component: engine fix-version: 2.5 Beta 1 priority: major qa: not enough information type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

With multiple connections simultaneously creating and dropping metadata objects, sometimes the lock manager terminates the server process due to an internal bugcheck. This seems to be related to the DSQL metadata cache locks handling.

Commits: 50adebd
@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

Fix Version: 2.5 Beta 1 [ 10251 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

resolution: Fixed [ 1 ]

@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 => Not enough information

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

@dyemanov dyemanov

Labels
affect-version: 2.5 Alpha 1 affect-version: 2.5 Initial component: engine fix-version: 2.5 Beta 1 priority: major qa: not enough information type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dyemanov @firebird-automations