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 "Larry West (JIRA)" <ji...@apache.org> on 2016/09/15 00:08:21 UTC
[jira] [Updated] (LOG4J2-1583) Nested logging call disrupts output
of outer logging call
[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Larry West updated LOG4J2-1583:
-------------------------------
Affects Version/s: (was: 2.6.1)
> Nested logging call disrupts output of outer logging call
> ---------------------------------------------------------
>
> Key: LOG4J2-1583
> URL: https://issues.apache.org/jira/browse/LOG4J2-1583
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5, 2.6, 2.6.2
> Environment: JVM 1.8.0_102, MacOS 10.11.6
> Reporter: Larry West
> Attachments: LOG4J-1583.tbz2, Log4j2ProblemDemo.java, log4j2.xml, pom.xml
>
>
> If a call to logger.info() invokes the toString() method on one of its parameters, and that toString() method invokes another method which has another, nested logging call, then the output of the outer call is mangled.
> This can be quite confusing as the nested logging may be conditional, or at DEBUG level, etc.
--
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