You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Venkateswararao Jujjuri (JV) (JIRA)" <ji...@apache.org> on 2016/09/28 16:12:20 UTC
[jira] [Updated] (BOOKKEEPER-924) addEntry() is susceptible to
spurious wakeups
[ https://issues.apache.org/jira/browse/BOOKKEEPER-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Venkateswararao Jujjuri (JV) updated BOOKKEEPER-924:
----------------------------------------------------
Assignee: Matteo Merli (was: Venkateswararao Jujjuri (JV))
> addEntry() is susceptible to spurious wakeups
> ---------------------------------------------
>
> Key: BOOKKEEPER-924
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-924
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.3.2
> Reporter: Venkateswararao Jujjuri (JV)
> Assignee: Matteo Merli
> Priority: Critical
> Fix For: 4.5.0
>
>
> LedgerHandle sync interface heavily depends on SyncCounter to convert async interfaces
> into sync interfaces.
> Usaylly
> SyncCounter.inc()
> asyncCall()
> SyncCOunter.block(0)
> The block code is.
> synchronized void block(int limit) throws InterruptedException {
> while (i > limit) {
> int prev = i;
> wait();
> if (i == prev) {
> break;
> }
> }
> }
> Since 'i' is going to be same as 'prev' on spurious wakeup, and wait() can return on spurious wakeups.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)