You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2020/02/21 20:39:00 UTC

[jira] [Updated] (NIFI-6064) MockComponentLog misplaces reported exceptions

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

Joe Witt updated NIFI-6064:
---------------------------
    Fix Version/s: 1.11.3

> MockComponentLog misplaces reported exceptions
> ----------------------------------------------
>
>                 Key: NIFI-6064
>                 URL: https://issues.apache.org/jira/browse/NIFI-6064
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.8.0, 1.9.0
>            Reporter: Sergei Zhirikov
>            Assignee: karthik kadajji
>            Priority: Minor
>             Fix For: 1.12.0, 1.11.3
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When MockComponentLog.error(String, Throwable) is called, the message is forwarded to CapturingLogger.error(String, Object, Object), which treats the Throwable passed as the last parameter as a regular message parameter and passes it as such to the LogMessage constructor. As the result, the Throwable ends up as the last element in LogMessage.args, instead of the LogMessage.throwable field, where it would be more appropriate.
> Note: I have only tested this with 1.8.0, but the relevant code in the master branch is the same, so I assume the issue applies to the latest version as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)