Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 12 Feb 2014 18:02:21 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12694294.1392050883130.31676.1392228141341@arcas>
In-Reply-To: <JIRA.12694294.1392050883130@arcas>
References: <JIRA.12694294.1392050883130@arcas>
Subject: [jira] [Commented] (ACCUMULO-2346) Make UtilWaitThread.sleep()
 reset interrupt status
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899355#comment-13899355 ] 

Christopher Tubbs commented on ACCUMULO-2346:
---------------------------------------------

There was a [mailing list thread|http://mail-archives.apache.org/mod_mbox/accumulo-dev/201311.mbox/%3CCAL5zq9a3Y+szSbr7qvHh2=dvQf7gwnbWn3m0As4COwJ=eiS8dg@mail.gmail.com%3E] regarding this back in November.

> Make UtilWaitThread.sleep() reset interrupt status
> --------------------------------------------------
>
>                 Key: ACCUMULO-2346
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2346
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>             Fix For: 1.7.0
>
>
> Look into making UtilWaitThread.sleep() reset the interrupt status by calling {{Thread.currentThread().interrupt()}}.  This seems like a good thing to do, it allows code that does not want to deal with the interrupt to pass it on.  The question is, does doing this cause new bugs?


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)