[
https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833414#comment-13833414
]
Orcun Simsek commented on CURATOR-79:
-------------------------------------
Also adding a test that fails.
{code:title=Test.java|borderStyle=solid}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
> InterProcessMutex doesn't clean up after interrupt
> --------------------------------------------------
>
> Key: CURATOR-79
> URL: https://issues.apache.org/jira/browse/CURATOR-79
> Project: Apache Curator
> Issue Type: Bug
> Reporter: Orcun Simsek
> Assignee: Jordan Zimmerman
> Priority: Blocker
>
> If the current thread is interrupted while acquiring the InterProcessMutex, a
> new node for the lock is created, InterruptException is thrown, and node is
> not deleted afterwards. Thus causing a deadlock.
> Curator should check the Interrupted state, and do the proper clean up.
> This issue was also discussed on:
> https://groups.google.com/forum/#!topic/curator-users/9ii5of8SbdQ
--
This message was sent by Atlassian JIRA
(v6.1#6144)
