- logback-dev - mailman3.qos.ch

[JIRA] Updates for LOGBACK-1711: Deadlock when using Virtual Threads
by QOS.CH (JIRA) 03 Dec '22

03 Dec '22

logback / LOGBACK-1711 [Open] Deadlock when using Virtual Threads ============================== 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-1711 ============================== Issue created ------------------------------ Gili created this issue on 03/Dec/22 9:52 AM Summary: Deadlock when using Virtual Threads Issue Type: Bug Affects Versions: 1.4.5 Assignee: Logback dev list Components: logback-core Created: 03/Dec/22 9:52 AM Priority: Blocker Reporter: Gili Description: Repro steps: # Unpack testcase.zip # Run the Testcase class # Application should deadlock at around the time it outputs "Progress: 340000" This issue is 100% reproducible and only occurs when using JDK 19 virtual threads. The bug seems to be triggered by *RollingFileAppender.rollover()*. Please note that using I/O inside synchronized blocks pins a carrier threads and this substantially reduces the performance of virtual threads. Please consider replacing such constructs with ReentrantLock or StampedLock as you have done elsewhere. The deadlock might have something to do with all carrier threads waiting to acquire a synchronized block, while the thread holding the lock is blocked waiting for an I/O response. I'm not sure why the latter never comes back though... ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1710) Ability to use <include> anywhere not only directly within <configuration>
by QOS.CH (JIRA) 02 Dec '22

02 Dec '22

1 0

[JIRA] Updates for LOGBACK-1710: Ability to use <include> anywhere not only directly within <configuration>
by QOS.CH (JIRA) 02 Dec '22

02 Dec '22

logback / LOGBACK-1710 [Open] Ability to use <include> anywhere not only directly within <configuration> ============================== 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-1710 ============================== Issue created ------------------------------ Missaka Iddamalgoda created this issue on 02/Dec/22 9:18 PM Summary: Ability to use <include> anywhere not only directly within <configuration> Issue Type: Improvement Assignee: Logback dev list Components: Joran, logback-classic Created: 02/Dec/22 9:18 PM Environment: I am writing a separate java project as a maven artifact that I can add as a dependency to other projects. This Project is just some special loggers that can be included in logback configuration by other projects as necessary. But what I am trying to achieve is these loggers are, I need the logs selected by these filters to only print in the particular appender but logs that match the logger but not accepted by the filter to be passed down to the root logger. Only way the logs not selected by the filter to be printed in the root logger is to make my current logger to set logger attribute `additivity="true"` but this results in also printing the logs selected by my new logger also be printed in the root logger as well. To fix this i have to add a deny filter to the appenders of root logger to deny the logs that matched my custom logger and appenders. So when I tried to include the deny filter to the appender using a <include> I get an error as java.lang.IllegalStateException: Logback configuration error detected: ERROR in ch.qos.logback.core.joran.spi.Interpreter@10:79 - no applicable action for [include], current ElementPath is [[configuration][appender][include]] Labels: configuration filter Priority: Major Reporter: Missaka Iddamalgoda Description: Would like to be able to use include withing tags like <appender> <logger> etc. Currently it only supports following. {code:xml} <configuration> <include/> </configuration> {code} But would like to have the following. {code:xml} <configuration> <appender> <include/> <include/> <encoder> </encoder> </appender> </configuration> {code} This allows other developers to not worry about the content and only use the provided includes to add new filters etc. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-302) Wrong date format in access log
by QOS.CH (JIRA) 29 Nov '22

29 Nov '22

1 0

[JIRA] (LOGBACK-1696) Log timestamps incorrect month format on en_AU.UTF-8
by QOS.CH (JIRA) 29 Nov '22

29 Nov '22

1 0

[JIRA] (LOGBACK-1696) Log timestamps incorrect month format on en_AU.UTF-8
by QOS.CH (JIRA) 29 Nov '22

29 Nov '22

1 0

[JIRA] (LOGBACK-1606) Bring Back Groovy Config and use SecureASTCustomizer to secure it
by QOS.CH (JIRA) 28 Nov '22

28 Nov '22

1 0

[JIRA] Updates for LOGBACK-1709: Double check that KeyPairValue serialized properly and passes HardenedInputStream
by QOS.CH (JIRA) 23 Nov '22

23 Nov '22

logback / LOGBACK-1709 [Open] Double check that KeyPairValue serialized properly and passes HardenedInputStream ============================== Here's what changed in this issue in the last few minutes. This issue has been created View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1709 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 23/Nov/22 8:57 PM Summary: Double check that KeyPairValue serialized properly and passes HardenedInputStream Issue Type: Bug Affects Versions: 1.3.5, 1.4.5 Assignee: Ceki Gülcü Components: logback-classic Created: 23/Nov/22 8:57 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1705) Upgrading logback from 1.2.6 to 1.3.0 stops logging
by QOS.CH (JIRA) 23 Nov '22

23 Nov '22

1 0

[JIRA] (LOGBACK-1708) Add the OpenSSF Scorecards GitHub Action
by QOS.CH (JIRA) 22 Nov '22

22 Nov '22

1 0