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

Posted to issues@drill.apache.org by "Daniel Barclay (Drill/MapR) (JIRA)" <ji...@apache.org> on 2014/12/31 21:10:13 UTC

[jira] [Updated] (DRILL-1915) Lilith code might be swallowing InterruptedException (not calling Thread.interrupt())

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

Daniel Barclay (Drill/MapR) updated DRILL-1915:
-----------------------------------------------
    Summary: Lilith code might be swallowing InterruptedException (not calling Thread.interrupt())  (was: Lilith code might be swallowing InterruptedException (not calling Thread.interrup()))

> Lilith code might be swallowing InterruptedException (not calling Thread.interrupt())
> -------------------------------------------------------------------------------------
>
>                 Key: DRILL-1915
>                 URL: https://issues.apache.org/jira/browse/DRILL-1915
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Daniel Barclay (Drill/MapR)
>
> It seems that the Lilith logging code catches InterruptedException (in some synchronization code) but doesn't call Thread.currentThread().interrupt() to re-set the interruption status (so that the interrupt request can be processed by the next code to check the interruption status).



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