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 the lock" Exception #505
Comments
We were able to get a lock dump also.
|
@phishman3579 can you share a unit test which reproduces the issue? We are busy with customer work and so unlikely to get this in the short term (and apologies for such a slow response - this one fell between the cracks). If you would like us to prioritise it please review the support offerings at https://chronicle.software/openhft-support/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From
VanillaChronicleHash
I've been seeing this exception occasionally when using chronicle map. From the previous issues (#376) the problem was thought to be fixed. I am currently using version 3.24ea3. We've been experimenting locally and have found that making the lock a class local field seems to have mitigated the exception.
See
Chronicle-Map/src/main/java/net/openhft/chronicle/hash/impl/VanillaChronicleHash.java
Line 93 in 84f4a8e
Chronicle-Map/src/main/java/net/openhft/chronicle/hash/impl/VanillaChronicleHash.java
Line 95 in 84f4a8e
Is there a reason why that lock is a
static
field?The text was updated successfully, but these errors were encountered: