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

[JIRA] (LOGBACK-1756) Change LoggerContext to use MDCAdapter instead of LogbackMDCAdapter
by logback developers list 28 Jul '23

28 Jul '23

1 0

Setting MDCAdapter
by logback developers list 27 Jul '23

27 Jul '23

Hi, I've come across this issue recently https://github.com/line/armeria/issues/5045 where Armeria tries to set a non-thread-local MDCAdapter. This broke in logback 1.4.8 where MDCAdapter is created at logger creation time. Was wondering if there's something to fix in Logback to make this possible without a hacky workaround? Thanks, Ric Mariano

1 0

[JIRA] (LOGBACK-1756) Change LoggerContext to use MDCAdapter instead of LogbackMDCAdapter
by logback developers list 23 Jul '23

23 Jul '23

1 0

[JIRA] (LOGBACK-1756) Change LoggerContext to use MDCAdapter instead of LogbackMDCAdapter
by logback developers list 23 Jul '23

23 Jul '23

1 0

[JIRA] (LOGBACK-1754) OverlappingFileLockException when using prudent mode
by logback developers list 19 Jul '23

19 Jul '23

1 0

[JIRA] (LOGBACK-1754) OverlappingFileLockException when using prudent mode
by logback developers list 19 Jul '23

19 Jul '23

1 0

[JIRA] (LOGBACK-1756) Change LoggerContext to use MDCAdapter instead of LogbackMDCAdapter
by logback developers list 18 Jul '23

18 Jul '23

1 0

[JIRA] (LOGBACK-1746) insertFromJNDI resolves AFTER include in 1.4.x
by logback developers list 17 Jul '23

17 Jul '23

1 0

[JIRA] Updates for LOGBACK-1759: LoggerContext.reset() closes Jansi-OutputStream
by logback developers list 17 Jul '23

17 Jul '23

logback / LOGBACK-1759 [Open] LoggerContext.reset() closes Jansi-OutputStream ============================== 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-1759 ============================== Issue created ------------------------------ Wolfgang F. Riedl created this issue on 17/Jul/23 12:34 Summary: LoggerContext.reset() closes Jansi-OutputStream Issue Type: Bug Affects Versions: 1.3.8 Assignee: Logback dev list Components: logback-core Created: 17/Jul/23 12:34 Environment: h1. Description For my tests, I am reloading my Logback configuration via the following code snippet: {code:java} loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory configurator = new JoranConfigurator() configurator.setContext(loggerContext) loggerContext.reset() configurator.doConfigure(runResourcesPath.resolve("path.xml").toFile) {code} However, a call to loggerContext.reset() will, if configured with Jansi, call close() on the OutputStream of a ConsoleAppender (c.f. OutputStreamAppender.closeOutputStream()). This will prevent any more writing being done to this stream (i.e. the Jansi stream). h1. Expected Behaviour On loggerContext.reset(), a ConsoleAppender configured with Jansi should not close its output stream (as this is the Jansi stream). If configured without Jansi the stream can be closed without problems. h1. Environment * Logback: 1.3.7 and 1.3.8 * Jansi: 1.8 and 2.4.0 * Java: 1.8 and 11 * Windows 10 Priority: Critical Reporter: Wolfgang F. Riedl ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1758) loggerContext NPE in classic.LoggerContext.getMDCAdapter()
by logback developers list 13 Jul '23

13 Jul '23

1 0