You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2016/06/02 20:27:59 UTC
[jira] [Commented] (LOG4J2-1406) 2.6 is re-logging prior throwable
instead of logging the throwable that is currently passed in by application
code
[ https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312991#comment-15312991 ]
Ralph Goers commented on LOG4J2-1406:
-------------------------------------
Thanks for the patch! This looks like a pretty simple fix and should be included in the 2.6.1 release planned for this weekend.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org