[jira] [Updated] (NIFI-9734) Standardize Bulletin Exception Messages

["Joe Gresock (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-9734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Gresock updated NIFI-9734:
------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Standardize Bulletin Exception Messages
> ---------------------------------------
>
>                 Key: NIFI-9734
>                 URL: https://issues.apache.org/jira/browse/NIFI-9734
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.14.0
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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:
> {noformat}
> 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
> {noformat}
> 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:
> {noformat}
> 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
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)