- logback-dev - mailman3.qos.ch

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

15 Mar '22

1 0

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

15 Mar '22

1 0

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

14 Mar '22

1 0

[JIRA] Updates for LOGBACK-1621: no applicable action for [root], current ElementPath is [[configuration][root]]
by QOS.CH (JIRA) 12 Mar '22

12 Mar '22

logback / LOGBACK-1621 [Open] no applicable action for [root], current ElementPath is [[configuration][root]] ============================== 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-1621 ============================== Issue created ------------------------------ Chiiwen Liou created this issue on 12/Mar/22 7:29 AM Summary: no applicable action for [root], current ElementPath is [[configuration][root]] Issue Type: Bug Affects Versions: 1.2.11 Assignee: Logback dev list Components: logback-access Created: 12/Mar/22 7:29 AM Environment: Windows 11: Java 8 logback 1.2.11 slf4j 1.7.36 Labels: configuration Priority: Minor Reporter: Chiiwen Liou Description: java code with logback.xml failed withFailed java code with logback.xml failed with 22:01:51,235 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@14:22 - no applicable action for [root], current ElementPath is [[configuration][root]] 22:01:51,235 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@15:32 - no applicable action for [appender-ref], current ElementPath is [[configuration][root][appender-ref]] If I move logback to classpath and java code run fine with final Logger logger = LoggerFactory.getLogger(LogbackExample.class); logger.info("Hello World"); java code:----- final Logger logger = LoggerFactory.getLogger(LogbackExample.class); LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator configurator = new JoranConfigurator(); lc.reset(); configurator.setContext(lc); configurator.doConfigure("lib/logback.xml"); logger.info("Hello World"); logback.xml:----- <configuration scan="true" scanPeriod="60 seconds" debug="true"><configuration scan="true" scanPeriod="60 seconds" debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>%d\\{HH:mm:ss.SSS} [%thread] %-5level %logger\\{5} - %msg%n</pattern> </encoder> </appender> <root level="debug"> <appender-ref ref="STDOUT" /> </root> </configuration> ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1620: log messages in contextDestroyed does not work anymore
by QOS.CH (JIRA) 11 Mar '22

11 Mar '22

logback / LOGBACK-1620 [Open] log messages in contextDestroyed does not work anymore ============================== 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-1620 ============================== Issue created ------------------------------ John Pace created this issue on 11/Mar/22 10:02 PM Summary: log messages in contextDestroyed does not work anymore Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Created: 11/Mar/22 10:02 PM Priority: Major Reporter: John Pace Description: I am using slf4j 1.7.31 and logback 1.2.3 to log messages in a application for Apache Tomcat. I added the annotation @WebListener to one class, which handle various tasks on start/shutdown of the application. Here are the important parts of this class: {code}@WebListener public class AutoLoad implements ServletContextListener { private static final Logger log = LoggerFactory.getLogger(AutoLoad.class); public void contextInitialized(ServletContextEvent event) { log.info("Starting {}", APP_NAME); } public void contextDestroyed(ServletContextEvent event) { log.info("Shutting down {}", APP_NAME); if (LoggerFactory.getILoggerFactory() instanceof LoggerContext) { ((LoggerContext) LoggerFactory.getILoggerFactory()).stop(); } } }\{code} I always see the starting-message. But since some versions of logback I no longer see the shutdown-message. It still works, if I replace logback with slf4j-simple. This is possibly related: I had to add this line > LoggerFactory.getILoggerFactory()).stop(); because I suddently got warning on shutdown. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1530) Fluent Logging no longer works with 1.3.0-alpha5
by QOS.CH (JIRA) 09 Mar '22

09 Mar '22

1 0

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

05 Mar '22

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 05 Mar '22

05 Mar '22

1 0

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

04 Mar '22

1 0

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

04 Mar '22

1 0