[NIFI-9734] Standardize Bulletin Exception Messages

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.14.0
• Component/s: Core Framework
• Assignee: David Handermann
• Reporter: David Handermann
• Created: 28/Feb/22 15:46
• Updated: 01/Mar/22 11:50
• Resolved: 01/Mar/22 11:50

Description

NiFi 1.14.0 included improvements to bulletin log messages that incorporated the Java Exception class and message for each cause in the stack trace.

The current implementation lists the root cause first and the direct cause last, with each cause associated as follows:

java.net.ConnectionException: Connection refued
- causes: com.exceptionfactory.socketbroker.BrokeredConnectException: Proxy Address connection failed
- causes: org.apache.nifi.processors.standard.socket.ClientConnectException: SSH Client connection failed

Although this approach is technically correct, it does not follow the standard Java logging convention where the direct cause is listed first and the root cause is listed last. The order should be reversed so that the log output reads as follows:

org.apache.nifi.processors.standard.socket.ClientConnectException: SSH Client connection failed
- Caused by: com.exceptionfactory.socketbroker.BrokeredConnectException: Proxy Address connection failed
- Caused by: java.net.ConnectionException: Connection refued

Issue Links

• is related to: NIFI-4344 Improve bulletin messaging with exception details
• links to: GitHub Pull Request #5813