November 2018 - logback-dev

removing context selectors will break our libraries and applications
by Garret Wilson 28 Apr '19

28 Apr '19

Hi, I've been pretty deep inside the Logback code. In fact I wrote a comprehensive explanation on the bootstrap procedure here: https://stackoverflow.com/a/38317149/421049 We've created a library called Csar that allows one to configure various configuration "contexts" within the same JVM, for a program that has different locales at the same time, or different logging configurations for different users, etc. I explain this all at https://dzone.com/articles/creating-local-globals-with-csar . Our Clogr library used Csar to allow different logging configurations (or even different logging libraries!) to be set up for different parts of the application. (Imagine a server with different user sessions, each session being logged to a different file.) We got this working great for Logback. In fact we integrated it into our software development course; read about it here: https://clogr.io/learn (See the section on Clogr and compartmentalized configurations with Logback at the bottom.) The problem is that the initial bootstrap sequence of Logback was brittle, relying on a static class that could appear across modules. The appearance of the Java 9+ module system prohibits this altogether. But I had already created a ticket https://jira.qos.ch/browse/LOGBACK-1196 for how to fix this, long before the Java system was released, using the standard service provider mechanism. But now I see at https://logback.qos.ch/news.html that Logback will remove contexts altogether. This will break our ability to configure loggers separately in our application, and to use Clogr to manage them. Why remove this? There was nothing wrong with the simple context selection. The problem was how it was configured, using a static classes that had to be placed in a module outside its package. Just implement https://jira.qos.ch/browse/LOGBACK-1196, please. Don't break our application. I even provide much of the code to do this at LOGBACK-1196. What can we do to keep this from being removed and breaking our library? Why do we need to remove it in the first place? Why not fix it? (Ironically I was just told that Log4j 2 supports contexts, so maybe our application will have to switch back to Log4j. But I would prefer to have Clogr support both Logback and Log4j 2. There is no reason to remove this capability from Logback.) As I mentioned two years ago in LOGBACK-1196, I'm willing to contribute to fixing this. Let me know how to go forward. Thanks, Garret Wilson President GlobalMentor, Inc.

2 3

JDK 12 build 22 is now available at : - jdk.java.net/12/
by Rory O'Donnell 30 Nov '18

30 Nov '18

Hi Ceki, *NOTE:- *The JDK 12 schedule <http://openjdk.java.net/projects/jdk/12/> rampdown phase 1 of the release is coming up in a few weeks on Dec. 13, 2018. ** *JDK 12 Early Access build 22 **is now available **at : - jdk.java.net/12/* * Release Note updates since last email * * o Build 21 - Deprecating the default keytool -keyalg value (JDK-8212003) o Build 21 - Change to X25519 and X448 encoded private key format (JDK-8213363) o Build 20 - New command-line flag for more extensive error reporting in crash logs (JDK-8211845) o Build 20 -Initial Value of user.timezone System Property Changed (JDK-8185496) * JEPs proposed for JDK 12 : o JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector(Experimental) <http://openjdk.java.net/jeps/189> o JEP 334: JVM Constants API <http://openjdk.java.net/jeps/334> o JEP 344: Abortable Mixed Collections for G1 <http://openjdk.java.net/jeps/344> o JEP 346: Promptly Return Unused Committed Memory from G1 <http://openjdk.java.net/jeps/346> * JEPs targeted to JDK 12, so far o JEP 230: Microbenchmark Suite <https://openjdk.java.net/jeps/230> o JEP 325: Switch Expressions (Preview) <http://openjdk.java.net/jeps/325> o JEP 326: Raw String Literals (Preview) <http://openjdk.java.net/jeps/326> o JEP 340: One AArch64 Port, Not Two <http://openjdk.java.net/jeps/340> o JEP 341: Default CDS Archives <http://openjdk.java.net/jeps/341> Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1442) Adding "originalFileName" token to FileNamePattern or TimeBasedRollingPolicy
by QOS.CH (JIRA) 29 Nov '18

29 Nov '18

1 0

[JIRA] (LOGBACK-1442) Adding "originalFileName" token to FileNamePattern or TimeBasedRollingPolicy
by QOS.CH (JIRA) 29 Nov '18

29 Nov '18

1 0

[JIRA] (LOGBACK-1442) Adding "originalFileName" token to FileNamePattern or TimeBasedRollingPolicy
by QOS.CH (JIRA) 28 Nov '18

28 Nov '18

Anton Pryamostanov created LOGBACK-1442: ------------------------------------------- Summary: Adding "originalFileName" token to FileNamePattern or TimeBasedRollingPolicy Key: LOGBACK-1442 URL: https://jira.qos.ch/browse/LOGBACK-1442 Project: logback Issue Type: Improvement Components: logback-classic Environment: Let's consider the below example: {code:xml} <appender name="OutputInfo" class="ch.qos.logback.classic.sift.SiftingAppender"> <filter class="ch.qos.logback.classic.filter.LevelFilter"> <level>ERROR</level> <onMatch>ACCEPT</onMatch> <onMismatch>DENY</onMismatch> </filter> <discriminator> <key>automaticThreadName</key> <defaultValue>Unnamed Thread</defaultValue> </discriminator> <discriminator> <key>inputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <discriminator> <key>outputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <sift> <appender name="${automaticThreadName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./LOGS/${inputQueueName}/${outputQueueName}/ERROR/${automaticThreadName}_ERROR_TODAY.log</file> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>%d{yyyy-MM-dd HH:mm:ss} %mdc [%thread] %level %logger{35} - %msg%n</Pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>./LOGS/${inputQueueName}/${outputQueueName}/ERROR/ARCHIVE/%d{yyyyMMdd, aux}/${automaticThreadName}_%d{yyyyMMdd}_ERROR.zip</FileNamePattern> </rollingPolicy> </appender> </sift> </appender> {code} It is not a valid example because FileNamePattern of TimeBasedRollingPolicy does not support MDC tokens like the SiftingAppender supports. This is causing a significant limitation for SiftingAppender log archiving - a diversity of file names of SiftingAppender can be archived only into a narrow list of archives due to TimeBasedRollingPolicy not supporting MDC tokens. This can be easily fixed just by adding 3 tokens into TimeBasedRollingPolicy FileNamePattern, which will represent: - %q - qualified file name of original physical file, e.g. ./logs/thread1/20181115/thread1_errors.log - %f - only file name of original physical file, e.g. "thread1_errors.log" - %p - only path of original physical file, e.g. "./logs/thread1/20181115/" Therefore the above config will look like: {code} <appender name="OutputInfo" class="ch.qos.logback.classic.sift.SiftingAppender"> <filter class="ch.qos.logback.classic.filter.LevelFilter"> <level>ERROR</level> <onMatch>ACCEPT</onMatch> <onMismatch>DENY</onMismatch> </filter> <discriminator> <key>automaticThreadName</key> <defaultValue>Unnamed Thread</defaultValue> </discriminator> <discriminator> <key>inputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <discriminator> <key>outputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <sift> <appender name="${automaticThreadName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./LOGS/${inputQueueName}/${outputQueueName}/ERROR/${automaticThreadName}_ERROR_TODAY.log</file> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>%d{yyyy-MM-dd HH:mm:ss} %mdc [%thread] %level %logger{35} - %msg%n</Pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>%q.zip</FileNamePattern> </rollingPolicy> </appender> </sift> </appender> {code} Reporter: Anton Pryamostanov Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 27 Nov '18

27 Nov '18

1 0

[JIRA] (LOGBACK-1441) Name of ThresholdFilter given in logback.xml is ignored
by QOS.CH (JIRA) 27 Nov '18

27 Nov '18

1 0

[JIRA] (LOGBACK-1441) Name of ThresholdFilter given in logback.xml is ignored
by QOS.CH (JIRA) 27 Nov '18

27 Nov '18

Máté Kovács created LOGBACK-1441: ------------------------------------ Summary: Name of ThresholdFilter given in logback.xml is ignored Key: LOGBACK-1441 URL: https://jira.qos.ch/browse/LOGBACK-1441 Project: logback Issue Type: Bug Affects Versions: 1.3.0-alpha4 Environment: Reporter: Máté Kovács Assignee: Logback dev list Priority: Minor I have a logback.xml. A fragment of it is: <filter name="FileAppenderThresholdFilter" class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>${LOGGER_SDK_FILE_APPENDER_LOGLEVEL:-OFF}</level> </filter> If I obtain the ThresholdFilter object from java code, the name of it is null. I am sure I find the right object. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1440) ajouter mesaj özeticisi
by QOS.CH (JIRA) 23 Nov '18

23 Nov '18

Ceki Gülcü created LOGBACK-1440: ----------------------------------- Summary: ajouter mesaj özeticisi Key: LOGBACK-1440 URL: https://jira.qos.ch/browse/LOGBACK-1440 Project: logback Issue Type: Sub-task Reporter: Ceki Gülcü Assignee: Ceki Gülcü -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1439) Allow offline verification of configuration files
by QOS.CH (JIRA) 22 Nov '18

22 Nov '18

Ceki Gülcü created LOGBACK-1439: ----------------------------------- Summary: Allow offline verification of configuration files Key: LOGBACK-1439 URL: https://jira.qos.ch/browse/LOGBACK-1439 Project: logback Issue Type: Sub-task Reporter: Ceki Gülcü Assignee: Ceki Gülcü -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0