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/14 23:54:21 UTC

[jira] [Created] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

Larry West created LOG4J2-1583:
----------------------------------

             Summary: 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.6.2, 2.6.1, 2.6, 2.5
         Environment: JVM 1.8.0_102, MacOS 10.11.6
            Reporter: Larry West


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