[
https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313310#comment-15313310
]
Remko Popma commented on LOG4J2-1406:
-------------------------------------
Thanks for raising this issue!
I believe the null check is necessary to verify that the throwable has not
been set explicitly.
The underlying cause is that the throwable is not always correctly cleared
when the message is reused, and it's better to fix that instead.
> 2.6 is re-logging prior throwable instead of logging the throwable that is
> currently passed in by application code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1406
> URL: https://issues.apache.org/jira/browse/LOG4J2-1406
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Trask Stalnaker
> Priority: Critical
>
> Hi,
> I just want to make sure you saw the issue I submitted PR for a couple days
> ago. It seems a very serious issue in 2.6:
> https://github.com/apache/logging-log4j2/pull/31
> Thanks,
> Trask
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
