You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/04 17:35:25 UTC

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

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

ASF GitHub Bot commented on NIFI-1636:
--------------------------------------

Github user olegz commented on the pull request:

    https://github.com/apache/nifi/pull/285#issuecomment-205353808
  
    They were logged at DEBUG only level and that was the issue since you would not be able to see them, but now if there is an error the stack trace will be printed


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