You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2015/12/22 16:22:46 UTC

[jira] [Resolved] (CURATOR-283) LockInternals does not deal with spurious weakup?

     [ https://issues.apache.org/jira/browse/CURATOR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-283.
--------------------------------------
    Resolution: Invalid

Jira is best to report problems/issues. If this is causing an issue please create a new Jira with details and an example of the problem. For discussions of Curator details, please use the @user or @dev mailing list.

In this case, there's no reason to have such a coarse sync. The code works fine as it is AFAIK. Is there a problem that you are seeing?

> LockInternals does not deal with spurious weakup?
> -------------------------------------------------
>
>                 Key: CURATOR-283
>                 URL: https://issues.apache.org/jira/browse/CURATOR-283
>             Project: Apache Curator
>          Issue Type: Test
>          Components: Recipes
>            Reporter: csulyj
>            Priority: Trivial
>
> I don't understand why method internalLockLoop doesn't not deal with spurious weakup?
> I think it should be like this : 
>  synchronized (obj) {
>      while (condition does not hold)
>         obj.wait(timeout);
>          ... // Perform action appropriate to condition
>  }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)