[
https://issues.apache.org/jira/browse/CURATOR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stig Rohde Døssing resolved CURATOR-401.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.0.0
This looks like it was resolved in 4.0.0, marking as "fixed".
> Make InterProcessMutex.isOwnedByCurrentThread public
> ----------------------------------------------------
>
> Key: CURATOR-401
> URL: https://issues.apache.org/jira/browse/CURATOR-401
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Affects Versions: 2.12.0
> Reporter: Stig Rohde Døssing
> Priority: Minor
> Fix For: 4.0.0
>
>
> It is useful in some cases to be able to tell if the current thread holds the
> lock before calling acquire. I have some components using InterProcessMutex
> for coordination that are intended to run in different JVMs in production.
> I'd like to be able to write an integration test that runs them in the same
> JVM in different threads, and verify that the lock is held by the expected
> component at certain points in the code.
> Using InterProcessMutex.isAcquiredInThisProcess is not a good replacement in
> this case, and acquiring/releasing the lock unnecessarily also doesn't seem
> like a good solution.
> InterProcessMutex already supports this functionality, but the method is
> package private.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
