[jira] [Resolved] (LOG4J2-2975) SLF4J fluent API fails to capture call site location due to missing LoggingEventAware implementation

["Piotr Karwasz (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Karwasz resolved LOG4J2-2975.
-----------------------------------
    Resolution: Fixed

[~daniel.gray],

There is a new module {{log4j-slf4j20-impl}} in version {{2.18.1-SNAPSHOT}} available on [Apache Snapshots|https://repository.apache.org/snapshots]. Can you check if it solves your problem and close the issue?

> SLF4J fluent API fails to capture call site location due to missing LoggingEventAware implementation
> ----------------------------------------------------------------------------------------------------
>
>                 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
>            Assignee: Piotr Karwasz
>            Priority: Major
>             Fix For: 2.19.0
>
>
> 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.20.10#820010)