You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Daniel Gray (Jira)" <ji...@apache.org> on 2020/12/11 11:54:00 UTC

[jira] [Created] (LOG4J2-2975) Lambda expression call with log4j slf4j bridge logs the wrong line number

Daniel Gray created LOG4J2-2975:
-----------------------------------

             Summary: Lambda expression call with log4j slf4j bridge logs the wrong line number
                 Key: LOG4J2-2975
                 URL: https://issues.apache.org/jira/browse/LOG4J2-2975
             Project: Log4j 2
          Issue Type: Bug
          Components: SLF4J Bridge
    Affects Versions: 2.13.3
            Reporter: Daniel Gray


The logger outputs the wrong log line (120 for INFO, 117 for DEBUG, etc.) instead of the line in the program that generated the log, when running with the slf4j bridge. *This causes potential confusion when a person debugging something is reading the logs as the line numbers are wrong!*

I have prepared 2 simple CLI apps to show the correct behavior (with only Log4J) and the incorrect behavior (with the SLF4J bridge). Both are using the exact same configuration (log4j2.properties). The repositories of these sample projects are:

Good behavior with a pure log4j:
 [https://github.com/danielthegray/log4j-nobugsample]
 Wrong behavior with the slf4j bridge:
 [https://github.com/danielthegray/slf4j-bugsample]



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