- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1684) Unnecessary synchronization in LogbackMDCAdapter
by QOS.CH (JIRA) 26 Sep '22

26 Sep '22

1 0

[JIRA] (LOGBACK-620) Performance improvement for LogbackMDCAdapter
by QOS.CH (JIRA) 26 Sep '22

26 Sep '22

1 0

[JIRA] (LOGBACK-1684) Unnecessary synchronization in LogbackMDCAdapter
by QOS.CH (JIRA) 25 Sep '22

25 Sep '22

1 0

[JIRA] Updates for LOGBACK-1684: Unnecessary synchronization in LogbackMDCAdapter
by QOS.CH (JIRA) 24 Sep '22

24 Sep '22

logback / LOGBACK-1684 [Open] Unnecessary synchronization in LogbackMDCAdapter ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1684 ============================== Issue created ------------------------------ Sami Korhonen created this issue on 24/Sep/22 12:04 PM Summary: Unnecessary synchronization in LogbackMDCAdapter Issue Type: Improvement Assignee: Logback dev list Components: logback-classic Created: 24/Sep/22 12:04 PM Labels: Performance Priority: Major Reporter: Sami Korhonen Description: LogbackMDCAdapter uses synchronization. Synchronization has been added to fix problems related to use of inheritable thread local (LOGBACK-434) Inheritable thread local was removed in commit aa7d584ecdb1638bfc4c7223f4a5ff92d5ee6273 to fix issues LOGBACK-422 and LOGBACK-624. Synchronization was not removed It seems that synchronization and clever use of atomicinteger are no longer required. Logback exposes MDC variables only using single value getter and a method that returns a copy. Removing synchronization could have significant impact on situations where you need to update MDC often. One such use case is reactive java, that requires one to update MDC between every task that logs. Synchronization does also cause problems with project loom. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Re: [logback-dev] logback 1.3.1 available but not tagged
by Boris Unckel 23 Sep '22

23 Sep '22

Hello Ceki, thank you, I can proceed now. Regards Boris > Ceki Gülcü <ceki(a)qos.ch> hat am 23.09.2022 00:14 CEST geschrieben: > > > Sorry about that. Issue was fixed a few moments ago. > -- > Ceki Gülcü > > Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch > > On 9/22/2022 8:36 PM, Boris Unckel wrote: > > Hello, > > > > I have found logback 1.3.1 in the news 2022-09-14 https://logback.qos.ch/news.html and published on Maven Central https://mvnrepository.com/artifact/ch.qos.logback/logback-classic/1.3.1 It is not announced yet http://mailman.qos.ch/pipermail/announce/2022/thread.html > > > > Unfortunately the last Github tag is 1.3.0 https://github.com/qos-ch/logback/tags/ (2022-09-22 18:33 UTC). Could you add that please? We need that downstream for reviews and qualified release notes. > > > > Thank you > > > > Regards > > Boris

1 0

logback 1.3.1 available but not tagged
by Boris Unckel 22 Sep '22

22 Sep '22

Hello, I have found logback 1.3.1 in the news 2022-09-14 https://logback.qos.ch/news.html and published on Maven Central https://mvnrepository.com/artifact/ch.qos.logback/logback-classic/1.3.1 It is not announced yet http://mailman.qos.ch/pipermail/announce/2022/thread.html Unfortunately the last Github tag is 1.3.0 https://github.com/qos-ch/logback/tags/ (2022-09-22 18:33 UTC). Could you add that please? We need that downstream for reviews and qualified release notes. Thank you Regards Boris

2 1

[JIRA] Updates for LOGBACK-1683: Logback OSGi Manifest declares exporting org.slf4j.impl package
by QOS.CH (JIRA) 22 Sep '22

22 Sep '22

logback / LOGBACK-1683 [Open] Logback OSGi Manifest declares exporting org.slf4j.impl package ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1683 ============================== Issue created ------------------------------ Dr. Domagoj Ćosić created this issue on 22/Sep/22 7:22 PM Summary: Logback OSGi Manifest declares exporting org.slf4j.impl package Issue Type: Bug Affects Versions: 1.3.1 Assignee: Logback dev list Components: logback-classic Created: 22/Sep/22 7:22 PM Environment: Found: Logback (OSGi) Manifest still declares that it exports org.slf4j.impl package (Export-Package clause) though the JAR does not contain that package any more. Expected: Logback Manifest does not declare that it exports org.slf4j.impl Priority: Major Reporter: Dr. Domagoj Ćosić ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1681) Applications and libraries broken with SLF4J 2.x.
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

1 0

[JIRA] Updates for LOGBACK-1682: Allow to configure the clock that is used to generate timestamps
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

logback / LOGBACK-1682 [Open] Allow to configure the clock that is used to generate timestamps ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1682 ============================== Issue created ------------------------------ Alonso Gonzalez created this issue on 20/Sep/22 11:45 AM Summary: Allow to configure the clock that is used to generate timestamps Issue Type: Improvement Affects Versions: 1.2.11, 1.3.1 Assignee: Logback dev list Components: logback-classic Created: 20/Sep/22 11:45 AM Priority: Major Reporter: Alonso Gonzalez Description: logback creates the timestamp of a LoggingEvent using: {code:java} timeStamp = System.currentTimeMillis(); {code} in 1.2.11 and {code:java} Instant instant = Clock.systemUTC().instant(); initTmestampFields(instant); {code} in 1.3.1. Thus the time of the server is used to generate the timestamp of an entry. In scenarios where this time is not correct, the application can not influence the timestamps. Log4j has a clock interface ({{org.apache.logging.log4j.core.util.Clock}}) that can be implemented to achieve this task. The clock implementation can apply offsets to the system time. Would it be possibe to use a configurable clock instead of Clock.systemUTC() in logback? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1681) Applications and libraries broken with SLF4J 2.x.
by QOS.CH (JIRA) 19 Sep '22

19 Sep '22

1 0