-
Notifications
You must be signed in to change notification settings - Fork 537
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
Failed to acquire exclusive lock on the table store file #641
Comments
Released in Chronicle-Queue-5.19.0, BOM-2.19.4 |
Hello, I posted a question on StackOverFlow ( https://stackoverflow.com/questions/77152872/chronicle-queue-failed-to-acquire-exclusive-lock-on-the-table-store-file ) which has the same error stack mentioned in this ticket. Can someone please help me there. |
Hello @anirudh-striim - please can you share with us a unit test that reproduces the issue? Please also create a new issue when sharing this unit test with us as this issue is now closed and marked as released. Once we have a unit test reproducing the issue we will be able to take a closer look. |
when run with:
it fails with the exception below, but when run with:
no exceptions are logged. Its a guess but this maybe due to optomizations put in the proxy class creation, to help startup times.
The text was updated successfully, but these errors were encountered: