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

Posted to commits@nifi.apache.org by "marco polo (JIRA)" <ji...@apache.org> on 2017/03/25 14:12:41 UTC

[jira] [Updated] (MINIFI-252) FILE_OPERATION_EXCEPTION not being logged or caught

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

marco polo updated MINIFI-252:
------------------------------
    Description: With no claim on a resource, FILE_OPERATION_EXCEPTION is thrown, but not logged or caught. It is silently dropped. Java has a concept of an uncaught exception handler. We need to implement something like this so that we can know what to do in this case. At the very least a log message should be generated and roll back the session if it is not.   (was: With no claim on a resource, FILE_OPERATION_EXCEPTION is thrown, but not logged or caught. It is silently dropped. Java has a concept of an uncaught exception handler. We need to implement something like this so that we can know what to do in this case. At the very least a log message should be generated. )

> FILE_OPERATION_EXCEPTION not being logged or caught
> ---------------------------------------------------
>
>                 Key: MINIFI-252
>                 URL: https://issues.apache.org/jira/browse/MINIFI-252
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: C++
>            Reporter: marco polo
>            Priority: Critical
>
> With no claim on a resource, FILE_OPERATION_EXCEPTION is thrown, but not logged or caught. It is silently dropped. Java has a concept of an uncaught exception handler. We need to implement something like this so that we can know what to do in this case. At the very least a log message should be generated and roll back the session if it is not. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)