You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
Interrupt thread after get lock, CountDownLatch is not reset while lock at the next time
reset CountDownLatch at method prepare(), code :
private synchronized void prepare() {
......
syncPoint = new CountDownLatch(1);
}
Interrupt thread after get lock, the field currentNode is null, cleanup will throw NullPointException
Allow it to be null, code :
private void cleanup() {
if(currentNode != null) {
//delete currentNode....
}
......
}
The text was updated successfully, but these errors were encountered:
1316151417
changed the title
DistributedLock Issues : Interrupt thread after get lock, CountDownLatch is not initialized while lock at the next time
DistributedLock Issues : Interrupt thread after get lock, CountDownLatch is not reset while lock at the next time
Apr 4, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Interrupt thread after get lock, CountDownLatch is not reset while lock at the next time
reset CountDownLatch at method prepare(), code :private synchronized void prepare() { ...... syncPoint = new CountDownLatch(1); }
Interrupt thread after get lock, the field currentNode is null, cleanup will throw NullPointException
Allow it to be null, code :private void cleanup() { if(currentNode != null) { //delete currentNode.... } ...... }
The text was updated successfully, but these errors were encountered: