You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/03 00:23:20 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=15541210#comment-15541210 ] 

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

Github user trixpan commented on the issue:

    https://github.com/apache/nifi/pull/285
  
    @rickysaltzer - is the PR still relevant? Would you mind if we close otherwise?


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