November 2022 - logback-dev

[JIRA] Updates for LOGBACK-1706: insertFromJNDI does not work in 1.4.4
by QOS.CH (JIRA) 18 Nov '22

18 Nov '22

logback / LOGBACK-1706 [Open] insertFromJNDI does not work in 1.4.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-1706 ============================== Issue created ------------------------------ Ove Hiltwein created this issue on 18/Nov/22 11:07 AM Summary: insertFromJNDI does not work in 1.4.4 Issue Type: Bug Affects Versions: 1.4.4 Assignee: Logback dev list Components: logback-classic Created: 18/Nov/22 11:07 AM Environment: Linux, Tomcat 10.0.23 Priority: Major Reporter: Ove Hiltwein Description: For our web application (tomcat 10.0.23) using logback-classic in versin 1.2.11, we define the log file name with the insertFromJNDI option as described in the documentation: in the logback config file: <insertFromJNDI env-entry-name="java:comp/env/loggingContextName" as="loggingContextName" /> <contextName>${loggingContextName}</contextName> <appender name="ERRORFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${logDir}/${loggingContextName}_error_%d\{yyyy-MM-dd}.log </fileNamePattern> <maxHistory>7</maxHistory> </rollingPolicy> <encoder> <pattern>%d\{ISO8601} %5p [%X\{session}] [%c]: %m%n</pattern> </encoder> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>WARN</level> </filter> </appender> The environment entry is defined in the web.xml: <env-entry> <env-entry-name>loggingContextName</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>server_v4</env-entry-value> </env-entry> This works nicely and as epxected. However, after upgrading to logback-classic version 1.4.4, the corresponding log information is written to a file loggingContextName_IS_UNDEFINED_error_<date>.log, and tomcat prints the following to the console during startup: -ERROR in ch.qos.logback.core.model.processor.DefaultProcessor@1390cc4c - Can't handle model of type class ch.qos.logback.core.model.InsertFromJNDIModel with tag: insertFromJNDI at line 5 ============================== 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) 16 Nov '22

16 Nov '22

1 0

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

14 Nov '22

1 0

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

14 Nov '22

1 0

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

14 Nov '22

1 0

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

14 Nov '22

1 0

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

14 Nov '22

1 0

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

13 Nov '22

1 0

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

11 Nov '22

logback / LOGBACK-1705 [Open] Upgrading logback from 1.2.6 to 1.3.0 stops 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-1705 ============================== Issue created ------------------------------ SHUBHAM GOSWAMI created this issue on 11/Nov/22 1:04 PM Summary: Upgrading logback from 1.2.6 to 1.3.0 stops logging Issue Type: Bug Affects Versions: 1.3.0 Assignee: Logback dev list Components: logback-classic Created: 11/Nov/22 1:04 PM Environment: In my web application Labels: logging Priority: Blocker Reporter: SHUBHAM Description: I am using 1.3.0 logback-classic version, my application stops logging. The logback.xml file maybe isn't even loaded (if I insert invalid xml or delete it, I get no errors). It works fine with logback 1.2.6. This works: logback-classic-1.2.6.jar + logback-core-1.2.6.jar + slf4j-api-1.7.36.jar This doesn't work: logback-classic-1.3.0.jar + logback-core-1.3.0.jar + slf4j-api-2.0.0.jar ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

New module/functionality for Native Image
by Dmitry Kubakhov 10 Nov '22

10 Nov '22

Hello logback team, My name is Dmitry. In our development process, we are using java, micronaut, and logback for logging. Right now we are planning to move to GraalVM, reactor, and use native-image. The current implementation of the AsyncAppender and RollingFileAppender has issues with native image - Logback Jira <https://jira.qos.ch/browse/LOGBACK-1550>. To fix this problem we are using modified AsyncAppender and RollingFileAppender for native image. We would like to share these changes, but we do not know the best way to do it. This native module from our point of view should not be in the main repository of the logback. There are 2 additional repositories - logback-extensions <https://github.com/qos-ch/logback-extensions> and logback-contrib <https://github.com/qos-ch/logback-contrib> - but they are not maintained anymore. At least, the last releases were in 2018. Please, can you share your thoughts on this? How we can bring these changes to the logback users/developers? Thank you in advance, Dmitry Kubakhov Senior Software Developer

1 0