March 2023 - logback-dev - mailman3.qos.ch

[JIRA] Updates for LOGBACK-1727: Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file.
by logback developers list 22 Mar '23

22 Mar '23

logback / LOGBACK-1727 [Open] Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file. ============================== 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-1727 ============================== Issue created ------------------------------ Lakshmikanth Reddy created this issue on 22/Mar/23 14:31 Summary: Logback: After upgrading to 1.3.6 with SLF4J 2.0.4, logs are being written to unknown.log file. Issue Type: Bug Affects Versions: 1.3.6 Assignee: Logback dev list Components: logback-core Created: 22/Mar/23 14:31 Labels: siftingAppender Priority: Major Reporter: Lakshmikanth Reddy Description: Hi Team, After upgrading the logback-classic and logback-core to 1.3.6 along with SLF4J to 2.0.4, the logs are being written to unknown.log file. Our config looks exactly like below. {code:java} <configuration> <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator"> <DefaultValue>unknown</DefaultValue> </discriminator> <sift> <appender name="FILE-${contextName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/${contextName}.log</File> <append>true</append> <immediateFlush>true</immediateFlush> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>${catalina.base}/logs/${contextName}.%i.log.zip</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>20MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS}|%-5level|${HOSTNAME}|%msg ||%class:%line %xException{full} %n</pattern> </encoder> </appender> </sift> </appender> <root level="INFO"> <appender-ref ref="SIFT" /> </root> </configuration> {code} Our previous version was: logback: 1.2.11 with SLF4J at version 1.7.36. Note: All the required config described in the documentation for JNDI is as is and has not changed. Any pointers to resolve this issue would be great help. Thanks, Lakshmikanth ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1595) Update Jansi library to 2.4.0
by logback developers list 20 Mar '23

20 Mar '23

1 0

[JIRA] (LOGBACK-1713) AppenderFactory not set in SiftingAppender
by logback developers list 16 Mar '23

16 Mar '23

1 0

[JIRA] (LOGBACK-1713) AppenderFactory not set in SiftingAppender
by QOS.CH (JIRA) 15 Mar '23

15 Mar '23

1 0

[JIRA] Updates for LOGBACK-1719: Support for Turbofilters in LoggingEventBuilder
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1719 [Open] Support for Turbofilters in LoggingEventBuilder ============================== 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-1719 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:03 PM Summary: Support for Turbofilters in LoggingEventBuilder Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:03 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1720: Flaky test failure observed
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1720 [Open] Flaky test failure observed ============================== 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-1720 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:03 PM Summary: Flaky test failure observed Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:03 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1721: Flaky test failure observed for SMTPAppender_GreenTest#testCustomEvaluator
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1721 [Open] Flaky test failure observed for SMTPAppender_GreenTest#testCustomEvaluator ============================== 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-1721 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:04 PM Summary: Flaky test failure observed for SMTPAppender_GreenTest#testCustomEvaluator Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:04 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1722: Provide conversion word for thread id (not just thread name)
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1722 [Open] Provide conversion word for thread id (not just thread name) ============================== 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-1722 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:04 PM Summary: Provide conversion word for thread id (not just thread name) Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:04 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1723: Allow customizing status messages (e.g. for structured logging)
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1723 [Open] Allow customizing status messages (e.g. for structured logging) ============================== 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-1723 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:04 PM Summary: Allow customizing status messages (e.g. for structured logging) Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:04 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1724: The logback-access tomcat valve won't allow externall configuration files to bespecified
by QOS.CH (JIRA) 14 Mar '23

14 Mar '23

logback / LOGBACK-1724 [Open] The logback-access tomcat valve won't allow externall configuration files to bespecified ============================== 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-1724 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Mar/23 2:05 PM Summary: The logback-access tomcat valve won't allow externall configuration files to bespecified Issue Type: Bug Assignee: Logback dev list Created: 14/Mar/23 2:05 PM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0