December 2017 - slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-393) Fix MDC issue with slf4j-log4j12
by QOS.CH (JIRA) 06 Dec '17

06 Dec '17

[ https://jira.qos.ch/browse/SLF4J-393?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-393: ---------------------------------- I agree this is not resolved. However, it has nothing to do with SLF4J-423. > Fix MDC issue with slf4j-log4j12 > -------------------------------- > > Key: SLF4J-393 > URL: https://jira.qos.ch/browse/SLF4J-393 > Project: SLF4J > Issue Type: Sub-task > Components: Implementations > Affects Versions: 1.7.22 > Environment: Incorrect parsing of the java.version system property in log4j 1.2 disables MDC. Enable log4j's MDC by reflection. > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Fix For: 1.7.23 > > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-423) 1.8.0-beta0 bug in log4j MDC handling
by QOS.CH (JIRA) 04 Dec '17

04 Dec '17

[ https://jira.qos.ch/browse/SLF4J-423?page=com.atlassian.jira.plugin.system.… ] Ralph Goers commented on SLF4J-423: ----------------------------------- If you are routing SLF4J to Log4j 2 you should not need the slf4j-log4j12 jar. You can use log4j-slf4j-impl to route slf4j directly to Log4j 2 and then log4j-1.2-api to route log4j api calls to Log4j 2. > 1.8.0-beta0 bug in log4j MDC handling > ------------------------------------- > > Key: SLF4J-423 > URL: https://jira.qos.ch/browse/SLF4J-423 > Project: SLF4J > Issue Type: Bug > Components: Unspecified > Affects Versions: 1.8.0-beta0 > Environment: Java 9 > Reporter: Brett Wooldridge > Assignee: SLF4J developers list > > When running with log4j 2.10.0, and using the slf4j-log4j12-1.8.0-beta0 release, the follow error is received: > {code:java} > java.lang.NoSuchFieldException: mdc > at java.base/java.lang.Class.getDeclaredField(Unknown Source) > at org.apache.log4j.MDCFriend.fixForJava9(MDCFriend.java:13) > at org.slf4j.log4j12.Log4jMDCAdapter.<clinit>(Log4jMDCAdapter.java:38) > at org.slf4j.log4j12.Log4j12ServiceProvider.initialize(Log4j12ServiceProvider.java:37) > at org.slf4j.LoggerFactory.bind(LoggerFactory.java:153) > at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:141) > at org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:413) > at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:405) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:354) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:380){code} > The MDC class in log4j-1.2-api-2.10.0.jar no longer contains a field named "mdc". (This is on Java 9). > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-393) Fix MDC issue with slf4j-log4j12
by QOS.CH (JIRA) 04 Dec '17

04 Dec '17

[ https://jira.qos.ch/browse/SLF4J-393?page=com.atlassian.jira.plugin.system.… ] Brett Wooldridge commented on SLF4J-393: ---------------------------------------- This is _not_ resolved. See SLF4J-423. > Fix MDC issue with slf4j-log4j12 > -------------------------------- > > Key: SLF4J-393 > URL: https://jira.qos.ch/browse/SLF4J-393 > Project: SLF4J > Issue Type: Sub-task > Components: Implementations > Affects Versions: 1.7.22 > Environment: Incorrect parsing of the java.version system property in log4j 1.2 disables MDC. Enable log4j's MDC by reflection. > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Fix For: 1.7.23 > > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-423) 1.8.0-beta0 bug in log4j MDC handling
by QOS.CH (JIRA) 04 Dec '17

04 Dec '17

Brett Wooldridge created SLF4J-423: -------------------------------------- Summary: 1.8.0-beta0 bug in log4j MDC handling Key: SLF4J-423 URL: https://jira.qos.ch/browse/SLF4J-423 Project: SLF4J Issue Type: Bug Components: Unspecified Affects Versions: 1.8.0-beta0 Reporter: Brett Wooldridge Assignee: SLF4J developers list When running with log4j 2.10.0, and using the slf4j-log4j12-1.8.0-beta0 release, the follow error is received: {code:java} java.lang.NoSuchFieldException: mdc at java.base/java.lang.Class.getDeclaredField(Unknown Source) at org.apache.log4j.MDCFriend.fixForJava9(MDCFriend.java:13) at org.slf4j.log4j12.Log4jMDCAdapter.<clinit>(Log4jMDCAdapter.java:38) at org.slf4j.log4j12.Log4j12ServiceProvider.initialize(Log4j12ServiceProvider.java:37) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:153) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:141) at org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:413) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:405) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:354) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:380){code} The MDC class in log4j-1.2-api-2.10.0.jar no longer contains a field named "mdc". -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] d186d5: failing OSGi/ServiceLoader integration
by Ceki Gulcu 02 Dec '17

02 Dec '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: d186d5fbd35d826fc85b5cd82b066d0655d6e1da https://github.com/qos-ch/slf4j/commit/d186d5fbd35d826fc85b5cd82b066d0655d6… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-12-02 (Sat, 02 Dec 2017) Changed paths: M integration/build.xml M integration/pom.xml M slf4j-api/src/main/resources/META-INF/MANIFEST.MF M slf4j-jdk14/src/main/resources/META-INF/MANIFEST.MF Log Message: ----------- failing OSGi/ServiceLoader integration

1 0

[qos-ch/slf4j] 3556e7: doc updates
by Ceki Gulcu 02 Dec '17

02 Dec '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 3556e7c87bb209e2dd99cf0aa771e0f6e28433b6 https://github.com/qos-ch/slf4j/commit/3556e7c87bb209e2dd99cf0aa771e0f6e284… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-12-02 (Sat, 02 Dec 2017) Changed paths: M slf4j-api/src/main/java/org/slf4j/LoggerFactory.java M slf4j-site/src/site/pages/news.html Log Message: ----------- doc updates

1 0

[qos-ch/slf4j] 5f0078: slf4j-api now requires Java 6
by Ceki Gulcu 02 Dec '17

02 Dec '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 5f00780faba08756932de6c165a153dd1dd7558a https://github.com/qos-ch/slf4j/commit/5f00780faba08756932de6c165a153dd1dd7… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-12-02 (Sat, 02 Dec 2017) Changed paths: M slf4j-api/src/main/resources/META-INF/MANIFEST.MF Log Message: ----------- slf4j-api now requires Java 6

1 0

[JIRA] (SLF4J-422) Have slf4j-log4j12 include extra arguments to Logger methods
by QOS.CH (JIRA) 01 Dec '17

01 Dec '17

[ https://jira.qos.ch/browse/SLF4J-422?page=com.atlassian.jira.plugin.system.… ] Eric Pabst commented on SLF4J-422: ---------------------------------- I'm going to start preparing a pull request. > Have slf4j-log4j12 include extra arguments to Logger methods > ------------------------------------------------------------ > > Key: SLF4J-422 > URL: https://jira.qos.ch/browse/SLF4J-422 > Project: SLF4J > Issue Type: Improvement > Components: Implementations > Affects Versions: 1.7.22 > Environment: All > Reporter: Eric Pabst > Assignee: SLF4J developers list > > The purpose of logging to slf4j is to allow code to log information without worrying about which implementation and format will be used for actual logging. In deployed environments, we prefer JSON logging using logstash to be consumed by Splunk, which handles JSON very nicely. However, for local development and testing, we prefer text output via log4j or logback-classic. > We often want to log extra fields to show up in the JSON output such as > {{\{ "timestamp": "2017...", "message": "Event X happened", "userName": "bob", "url": "http://..."}}} > To accomplish this, we use logstash's StructuredArgument to provide extra arguments to the Logger: > {{import static net.logstash.logback.argument.StructuredArguments.keyValue;}} > {{...}} > {{ LOGGER.info("Event X happened", keyValue("userName", "bob"), keyValue("url", "http://..."));}} > We don't want to include \{}'s in the message or else it would log the username and url both in the message and as separate JSON properties. > However, when binding to slf4j-log4j12, it is logged without these extra arguments: > {{INFO 2017... Event X happened}} > It would help immensely to include these extra arguments automatically if present: > INFO 2017... Event X happened username=bob url=http://... -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-422) Have slf4j-log4j12 include extra arguments to Logger methods
by QOS.CH (JIRA) 01 Dec '17

01 Dec '17

Eric Pabst created SLF4J-422: -------------------------------- Summary: Have slf4j-log4j12 include extra arguments to Logger methods Key: SLF4J-422 URL: https://jira.qos.ch/browse/SLF4J-422 Project: SLF4J Issue Type: Improvement Components: Implementations Affects Versions: 1.7.22 Environment: All Reporter: Eric Pabst Assignee: SLF4J developers list The purpose of logging to slf4j is to allow code to log information without worrying about which implementation and format will be used for actual logging. In deployed environments, we prefer JSON logging using logstash to be consumed by Splunk, which handles JSON very nicely. However, for local development and testing, we prefer text output via log4j or logback-classic. We often want to log extra fields to show up in the JSON output such as {{\{ "timestamp": "2017...", "message": "Event X happened", "userName": "bob", "url": "http://..."}}} To accomplish this, we use logstash's StructuredArgument to provide extra arguments to the Logger: {{import static net.logstash.logback.argument.StructuredArguments.keyValue;}} {{...}} {{ LOGGER.info("Event X happened", keyValue("userName", "bob"), keyValue("url", "http://..."));}} We don't want to include \{}'s in the message or else it would log the username and url both in the message and as separate JSON properties. However, when binding to slf4j-log4j12, it is logged without these extra arguments: {{INFO 2017... Event X happened}} It would help immensely to include these extra arguments automatically if present: INFO 2017... Event X happened username=bob url=http://... -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0