You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/03/01 09:02:18 UTC
[jira] [Commented] (LENS-954) await() is not inside loop in
FairPriorityBlockingQueue#waitUntilNotEmpty()
[ https://issues.apache.org/jira/browse/LENS-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173412#comment-15173412 ]
Hadoop QA commented on LENS-954:
--------------------------------
Applied patch: [LENS-954.patch|https://issues.apache.org/jira/secure/attachment/12790682/LENS-954.patch] and ran command: mvn clean install -fae. Result: Failure. Build Job: https://builds.apache.org/job/PreCommit-Lens-Build/308/
> await() is not inside loop in FairPriorityBlockingQueue#waitUntilNotEmpty()
> ---------------------------------------------------------------------------
>
> Key: LENS-954
> URL: https://issues.apache.org/jira/browse/LENS-954
> Project: Apache Lens
> Issue Type: Bug
> Components: server
> Reporter: Ted Yu
> Assignee: Ajay Yadava
> Priority: Minor
> Attachments: LENS-954.patch
>
>
> {code}
> private void waitUntilNotEmpty() throws InterruptedException {
> conditionalWaitLock.lock();
> try {
> notEmpty.await();
> } finally {
> conditionalWaitLock.unlock();
> }
> {code}
> From http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/Object.html#wait%28long%29 :
> A thread can wake up without being notified, interrupted, a so-called spurious wakeup. While this will rarely occur in practice, applications must guard against it by testing for the condition that should have caused the thread to be awakened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)