[slf4j-dev] [JIRA] (SLF4J-479) JUL-SLF4J Bridge - sourceMethod not logged
QOS.CH (JIRA)
noreply-jira at qos.ch
Sun Feb 16 23:26:00 CET 2020
[ https://jira.qos.ch/browse/SLF4J-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20258#comment-20258 ]
Anton Pryamostanov commented on SLF4J-479:
------------------------------------------
Kind reminder.
> JUL-SLF4J Bridge - sourceMethod not logged
> ------------------------------------------
>
> Key: SLF4J-479
> URL: https://jira.qos.ch/browse/SLF4J-479
> Project: SLF4J
> Issue Type: Bug
> Environment: JUL SLF4J Bridge 1.7.x
> Reporter: Anton
> Assignee: SLF4J developers list
>
> Consider an example from MSSQL JDBC Driver:
> [https://github.com/microsoft/mssql-jdbc/blob/77f9f1086049e5ea4ff11fb5434fdd348611ff1e/src/main/java/com/microsoft/sqlserver/jdbc/SQLServerConnection.java#L3253]
> {code:java}
> loggerExternal.entering(getClassNameLogging(), "commit");{code}
>
> _Actual result_: The *sourceMethodName* ("commit") is not passed to the underlying SLF4J implementation, via JUL-SLF4J Bridge.
> I.e. the sourceMethod is not logged in this case.
>
> _Expected result:_ JUL-SLF4J Bridge should pass sourceMethodName to SLF4J implementation.
> Please also check if there are any other such attributes affected.
> Suggested to fix in org.slf4j.bridge.SLF4JBridgeHandler.
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
More information about the slf4j-dev
mailing list