[prev in list] [next in list] [prev in thread] [next in thread]
List: drill-dev
Subject: [jira] [Created] (DRILL-1915) Lilith code might be swallowing InterruptedException (not calling Thre
From: "Daniel Barclay (Drill/MapR) (JIRA)" <jira () apache ! org>
Date: 2014-12-31 20:08:13
Message-ID: JIRA.12764416.1420056454000.123016.1420056493196 () Atlassian ! JIRA
[Download RAW message or body]
Daniel Barclay (Drill/MapR) created DRILL-1915:
--------------------------------------------------
Summary: Lilith code might be swallowing InterruptedException (not \
calling Thread.interrup()) 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)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic