[NIFI-1447] Improve exception logging for Processors

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Assignee: Oleg Zhurakousky
• Reporter: Oleg Zhurakousky
• Created: 28/Jan/16 15:56
• Updated: 22/Oct/16 10:36
• Resolved: 29/Jan/16 19:47

Description

Unfortunately while the title says "improve", I am logging it as a BUG for the following reasons.
A client reported an issue with one of the processors where the only visible message in both bulletin and logs is the message produced by ProcessLogger which does not seem to log a full stack trace. A typical pattern in current processor implementation is to have a significant code in onTrigger() method to be wrapped in try/catch where exception is logged and then re-thrown. Unfortunately it's not the case for this particular processor. As a result it is impossible to determine the cause of the root problem.
While immediate solution is to modify the specific Processor by wrapping its significant code in try/catch a better solution would be to improve ProcessLogger to log full stack trace whenever there is an error.

Issue Links

• relates to: NIFI-636 Processor Logger methods should use configured logging levels for message and throwable
• supercedes: NIFI-1636 Print entire stacktrace when unexpected exception occurs during onTrigger