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

Lock manager "out of room" error hides the real cause of this problem [CORE4631] #4945

Closed
firebird-automations opened this issue Dec 2, 2014 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

When the shared memory region backing the lock table cannot be remapped, the status vector returns the error message (lock manager out of room), but it lacks any low-level details (e.g. OS level error) causing this particular problem.

This is mostly fixed in v3, but some cases are not covered there either.

Commits: aa27116 44e57e3 FirebirdSQL/fbt-repository@41457bf FirebirdSQL/fbt-repository@848c27e

@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 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Beta 2 [ 10586 ]

Fix Version: 2.5.4 [ 10585 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Cannot be tested

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

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