[NIFI-1636] Print entire stacktrace when unexpected exception occurs during onTrigger

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Assignee: Ricky Saltzer
• Reporter: Ricky Saltzer
• Created: 16/Mar/16 20:42
• Updated: 22/Oct/16 10:36
• Resolved: 22/Oct/16 10:36

Description

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

java.lang.NumberFormatException: For input string: "five"

After

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)

Issue Links

• is superceded by: NIFI-1447 Improve exception logging for Processors
• links to: GitHub Pull Request #285
• links to: https://github.com/apache/nifi/pull/285