[CURATOR-375] Fix thread interruption being reported twice
Open
bug
imported-jira-issue
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
When a curator operation thread is interrupted, some classes (PersistentNode ConnectionState primarily) report the interruption in two ways at the same time - by re-marking the thread interruption status and throwing InterruptedException - this makes it look like the thread has been interrupted twice, rather than once.
---
Originally reported by thecoop1984, imported from: Fix thread interruption being reported twice
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.