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

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 13 - Early Access build 14 is available
by Rory O'Donnell 29 Mar '19

29 Mar '19

Hi Ceki, *OpenJDK builds *- JDK 13 - Early Access build 14 is available at http://jdk.java.net/13/ * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B13%22%3A%3…> * Release notes [1] * JDK 13 Schedule proposal accepted [2] o 2019/06/13 Rampdown Phase One o 2019/07/18 Rampdown Phase Two o 2019/08/08 Initial Release Candidate o 2019/08/22 Final Release Candidate o 2019/09/17 General Availability *jpackage EA * * This is an early access build of JEP 343: Packaging Tool <https://openjdk.java.net/jeps/343>, aimed at testing a prototype implementation of jpackage, which is a new tool for packaging self-contained Java applications along with a Java Runtime Environment. * Build 30 is now available http://jdk.java.net/jpackage/ * Please send feedback via e-mail to core-libs-dev(a)openjdk.java.net <mailto:core-libs-dev@openjdk.java.net> *Quality Outreach report for **March 2019* * The report for March 2019 is available here <https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+March…> * Thanks to all those contributed ! *Recent Blog:* A new (Japanese) era for Java! <https://blogs.oracle.com/java-platform-group/a-new-japanese-era-for-java> Rgds,Rory [1] http://jdk.java.net/13/release-notes [2] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002736.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

Release Announcement: General Availability of Java 12 / JDK 12
by Rory O'Donnell 20 Mar '19

20 Mar '19

Hi Ceki, *1) Release Announcement: General Availability of Java 12 / JDK 12 [1] * * JDK 12, the reference implementation of Java 12, is now Generally Available. * GPL-licensed OpenJDK builds from Oracle are available here: https://jdk.java.net/12 This release includes the following eight features: * JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector (Experimental) * JEP 230: Microbenchmark Suite * JEP 334: JVM Constants API * JEP 340: One AArch64 Port, Not Two * JEP 341: Default CDS Archives * JEP 344: Abortable Mixed Collections for G1 * JEP 346: Promptly Return Unused Committed Memory from G1 * JEP 325: Switch Expressions (Preview) <https://openjdk.java.net/jeps/325> Thanks to everyone who contributed JDK 12, whether by creating features or enhancements, logging bugs, or downloading and testing the early-access builds. *2) JDK 13 EA build 12, under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/13**.* * Proposed - Schedule for JDK 13 [2] o 2019/06/13 Rampdown Phase One o 2019/07/18 Rampdown Phase Two o 2019/08/08 Initial Release Candidate o 2019/08/22 Final Release Candidate o 2019/09/17 General Availability * Recent Bug fixes of Interest o Build 9: + 8214719: Deprecate -Xverify:none option + 8216360: Deprecate -XX:CompilationPolicyChoice o Build 10: + 8218995: Deprecate the -XX:FailOverToOldVerifier option o Build 12 : 8160247: Mark deprecated javax.security.cert APIs with forRemoval=true + 8220050: Deprecate -XX:-ThreadLocalHandshakes + Apache Lucene Reported - 8219448: split-if update_uses accesses stale idom data * Changes in this build [3] Rgds,Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002718.html [2] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002716.html [3] Changes <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B11%22%3A%3…> in this build -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1461) Tokenizer splits values containing special characters during variable substitution
by QOS.CH (JIRA) 19 Mar '19

19 Mar '19

Marek Šabo created LOGBACK-1461: ----------------------------------- Summary: Tokenizer splits values containing special characters during variable substitution Key: LOGBACK-1461 URL: https://jira.qos.ch/browse/LOGBACK-1461 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Marek Šabo Assignee: Logback dev list {code:java} <property name="pass_ok" value="myPassWith123#]@&"/> <property name="pass_split" value="myPassWith123}]@&"/> {code} Second password contains right curly brace which _ch.qos.logback.core.subst.Tokenizer_ uses a split-point. I guess all special chars from method _Tokenizer#handleLiteralState(..)_ ** will result in the same behavior: *$* *:* *\{* *}* I couldn't figure out how to escape the values properly. Tried approach with escaping from Layout Patterns, didn't help. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1000) MDC default value is not parsed
by QOS.CH (JIRA) 19 Mar '19

19 Mar '19

1 0

[JIRA] (LOGBACK-1297) Logback fails to roll once the file count exceeds 1000
by QOS.CH (JIRA) 15 Mar '19

15 Mar '19

1 0

[JIRA] (LOGBACK-1378) deadlock found
by QOS.CH (JIRA) 14 Mar '19

14 Mar '19

1 0

[JIRA] (LOGBACK-1362) NullPointerException in OutputStreamAppender on logback reconfiguratiuon
by QOS.CH (JIRA) 13 Mar '19

13 Mar '19

1 0

[JIRA] (LOGBACK-1460) totalSizeCap
by QOS.CH (JIRA) 07 Mar '19

07 Mar '19

huozhuang created LOGBACK-1460: ---------------------------------- Summary: totalSizeCap Key: LOGBACK-1460 URL: https://jira.qos.ch/browse/LOGBACK-1460 Project: logback Issue Type: Bug Affects Versions: 1.1.11 Environment: linux Reporter: huozhuang Assignee: Logback dev list Priority: Critical Attachments: 微信图片_20190307140658.png When the number of logs in a day is more than 1000, the logs cannot be deleted. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[contrib] Timeframe for releasing 0.1.6?
by Charles Honton 06 Mar '19

06 Mar '19

Are there any plans to release logback-contrib 0.1.6? Thanks, chas

1 0