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

Remove or improve the call to forcibly delete the database lock #9

Open
kerbymart opened this issue Feb 29, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@kerbymart
Copy link
Member

In the implementation of the DatabaseManager, when retrieving the environment the deleteLockingProcessAndGetEnvironment is called to forcibly "get" the environment, which is not the proper way to acquire the database.

A possible solution is to just remove it, or test for edge cases where remnant locks need to be removed when the process that holds the lock was not able to do the proper cleanup.

@kerbymart kerbymart added the enhancement New feature or request label Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant