- logback-dev - mailman3.qos.ch

[JIRA] Updates for LOGBACK-1619: Documentation error in Chapter 4
by QOS.CH (JIRA) 03 Mar '22

03 Mar '22

logback / LOGBACK-1619 [Open] Documentation error in Chapter 4 ============================== 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-1619 ============================== Issue created ------------------------------ Lenny Glassmann created this issue on 03/Mar/22 11:50 PM Summary: Documentation error in Chapter 4 Issue Type: Bug Assignee: Logback dev list Created: 03/Mar/22 11:50 PM Priority: Trivial Reporter: Lenny Glassmann Description: The section "Size and time based rolling policy" says "However, given that *{{SizeAndTimeBasedFNATP}}* offers a simpler configuration structure, we no longer document {{SizeAndTimeBasedFNATP}}." I think the first instance of {{SizeAndTimeBasedFNATP }}should be SizeAndTimeBasedRollingPolicy. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1618: port to the 1.2 branch
by QOS.CH (JIRA) 01 Mar '22

01 Mar '22

logback / LOGBACK-1618 [Open] port to the 1.2 branch ============================== 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-1618 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 01/Mar/22 7:40 PM Summary: port to the 1.2 branch Issue Type: Sub-task Assignee: Logback dev list Created: 01/Mar/22 7:40 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

ExecutorServiceUtil's use of Executors.defaultThreadFactory()
by Paul Summermatter 28 Feb '22

28 Feb '22

RE: Logback 1.2.10 All, We ran into a problem last week in a production environment where there were thousands of idle thread pool threads all with the name 'pool-NNN-thread'. We have been unable to reproduce the situation in non-prod, but we have discovered that logback makes use of thread pools but does not create a custom thread factory to name the threads as belonging to/initiated by logback. TimeBasedArchiveRemover is one example that makes use of a scheduled executor backed by Executors.defaultThreadFactory() (which provides only generic names for created threads). It would be very helpful if logback stopped using this factory and instead created its own, providing names for the threads that clearly indicate their creation was triggered by logback, e.g., "logback-NNN-thread". Is this something that has been previously discussed? Do folks agree that this would be useful? If so, should I file an enhancement request via JIRA? Any feedback or guidance would be appreciated. Regards, Paul

1 0

[JIRA] (LOGBACK-1617) Write logging file name with date pattern
by QOS.CH (JIRA) 28 Feb '22

28 Feb '22

1 0

[JIRA] (LOGBACK-1617) Write logging file name with date pattern
by QOS.CH (JIRA) 28 Feb '22

28 Feb '22

1 0

[JIRA] (LOGBACK-1617) Write logging file name with date pattern
by QOS.CH (JIRA) 28 Feb '22

28 Feb '22

1 0

[JIRA] Updates for LOGBACK-1617: Write logging file name with date pattern
by QOS.CH (JIRA) 28 Feb '22

28 Feb '22

logback / LOGBACK-1617 [Open] Write logging file name with date pattern ============================== 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-1617 ============================== Issue created ------------------------------ wshid created this issue on 28/Feb/22 8:02 AM Summary: Write logging file name with date pattern Issue Type: New Feature Assignee: Logback dev list Components: logback-core Created: 28/Feb/22 8:02 AM Priority: Minor Reporter: wshid Description: I wanted to use logback to +include the date in logging file name+, but I couldn't find the way with the code already developed. Like _log4j2_, I wanted *_RollingFileAppender_* to have a class that works with `[*DirectWriteRolloverStrategy*|https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/appender/rolling/DirectWriteRolloverStrategy.html]`, but it didn't exist. The contents I wanted to do are as follows. {code:java} log file in now(today) -> log_file.2022-02-28 log file in next day -> log_file.2022-03-01 the next two days -> log_file.2022-03-02 {code} Unlike the existing `*RollingFileAppender*`, it's a structure in which a new file with a date is created, +not a file rename+. This way is necessary for situations in which a problem may occur when rotating a file. To solve this problem which is caused by file rotation, I has developed a new '*DateNameFileAppender*'. Is there a way to solve it with the existing code that I couldn't find? While waiting for an answer to the above question, I'm going to pull-request on github. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1609) Bring back DBAppender or document how to proceed without it
by QOS.CH (JIRA) 26 Feb '22

26 Feb '22

1 0

[JIRA] (LOGBACK-1609) Bring back DBAppender or document how to proceed without it
by QOS.CH (JIRA) 26 Feb '22

26 Feb '22

1 0

[JIRA] (LOGBACK-1609) Bring back DBAppender or document how to proceed without it
by QOS.CH (JIRA) 25 Feb '22

25 Feb '22

1 0