You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/02/13 16:48:20 UTC

[jira] [Closed] (BOOKKEEPER-497) GcLedgersTest has a potential race

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

Ivan Kelly closed BOOKKEEPER-497.
---------------------------------

    
> GcLedgersTest has a potential race
> ----------------------------------
>
>                 Key: BOOKKEEPER-497
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-497
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.0
>
>         Attachments: 0001-BOOKKEEPER-497-GcLedgersTest-has-a-potential-race.patch
>
>
> The callbacks use Object#wait/notify without checking a condition. If the callback completes very quickly, the notify will happen before wait is ever called. The best solution is to use a CountDownLatch. Im seeing this problem when applying patch for BOOKKEEPER-205, probably due to a change in timing on the test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira