You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Kevin Doran (JIRA)" <ji...@apache.org> on 2017/05/01 18:18:04 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15991228#comment-15991228 ] 

Kevin Doran commented on MINIFI-252:
------------------------------------

I did a bit of research and found what appears to be a clean and simple way of doing this by using `std::set_terminate` to set a global handler: http://en.cppreference.com/w/cpp/error/set_terminate

Here is a detailed stack overflow answer containing some recommendations on the practice:
http://stackoverflow.com/a/2445569

> 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)