Mailing-List: contact commits-help@nifi.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.incubator.apache.org
Date: Mon, 23 Mar 2015 19:19:53 +0000 (UTC)
From: "Mark Payne (JIRA)" <jira@apache.org>
To: commits@nifi.incubator.apache.org
Message-ID: <JIRA.12783350.1426795083000.869.1427138393807@Atlassian.JIRA>
In-Reply-To: <JIRA.12783350.1426795083000@Atlassian.JIRA>
References: <JIRA.12783350.1426795083000@Atlassian.JIRA>
 <JIRA.12783350.1426795083649@arcas>
Subject: [jira] [Updated] (NIFI-450) FileSystemRepository's subtasks should
 catch Throwable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mark Payne updated NIFI-450:
----------------------------
    Attachment: 0001-NIFI-450-Catch-Throwable-from-all-implementations-of.patch

> FileSystemRepository's subtasks should catch Throwable
> ------------------------------------------------------
>
>                 Key: NIFI-450
>                 URL: https://issues.apache.org/jira/browse/NIFI-450
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>             Fix For: 0.1.0
>
>         Attachments: 0001-NIFI-450-Catch-Throwable-from-all-implementations-of.patch
>
>
> The DestroyExpiredArchiveClaims and BinDestructableClaims classes should wrap their implementations of the run() method with a try {...} catch (Throwable t) {...}
> If any Throwable escapes right now, it causes some pretty bad results, so we shouldn't let this happen. As a result, it could leave behind some files in the repo that won't be cleaned up until restart if a Throwable is thrown, but that's better than letting the thread die.


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