[jira] [Commented] (NIFI-1636) Print entire stacktrace when unexpected exception occurs during onTrigger

["Joseph Percivall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198134#comment-15198134 ] 

Joseph Percivall commented on NIFI-1636:
----------------------------------------

Unless I am missing something, I believe that is what the logger is for. It allows you to log the error and it will automatically print out the stack trace, for example in GetFile:

https://github.com/apache/nifi/blob/ba83bf9c051b337b98d7c8dfa322364c87ce5955/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/GetFile.java#L461-L461

> Print entire stacktrace when unexpected exception occurs during onTrigger
> -------------------------------------------------------------------------
>
>                 Key: NIFI-1636
>                 URL: https://issues.apache.org/jira/browse/NIFI-1636
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Ricky Saltzer
>            Assignee: Ricky Saltzer
>
> As of now the try/catch clause in the {{AbstractProcessor}} class doesn't print the entire stacktrace when a processor throws an unexpected exception. 
> Printing the entire stacktrace comes especially in handy when users are creating custom processors for internal use.
> The difference in information can be seen below:
> *Before*
> {code}
> java.lang.NumberFormatException: For input string: "five"
> {code}
> *After*
> {code}
> java.lang.NumberFormatException: For input string: "five"
> 	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> 	at java.lang.Integer.parseInt(Integer.java:580)
> 	at java.lang.Integer.parseInt(Integer.java:615)
> 	at TestException.main(TestException.java:5)
> {code}



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