September 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

[qos-ch/logback] b1fd71: ongoign work on model based configuration
by Ceki Gulcu 26 Sep '18

26 Sep '18

Branch: refs/heads/configModel Home: https://github.com/qos-ch/logback Commit: b1fd7115f8e7bcf2970df4d4cac4051b6ed5948c https://github.com/qos-ch/logback/commit/b1fd7115f8e7bcf2970df4d4cac4051b6e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-09-26 (Wed, 26 Sep 2018) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/joran/action/StatusListenerAction.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitConfigurationTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitShellModelAction.java Log Message: ----------- ongoign work on model based configuration **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.

1 0

[JIRA] (LOGBACK-1427) JMS Queue Appender
by QOS.CH (JIRA) 26 Sep '18

26 Sep '18

1 0

[JIRA] (LOGBACK-1427) JMS Queue Appender
by QOS.CH (JIRA) 26 Sep '18

26 Sep '18

1 0

[qos-ch/logback] 67aa09: ongoing work
by Ceki Gulcu 26 Sep '18

26 Sep '18

Branch: refs/heads/configModel Home: https://github.com/qos-ch/logback Commit: 67aa090f49bb2be5233c9aa192e26c6f607f00f2 https://github.com/qos-ch/logback/commit/67aa090f49bb2be5233c9aa192e26c6f60… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-08-13 (Mon, 13 Aug 2018) Changed paths: M logback-classic/pom.xml R logback-classic/src/test/java/ch/qos/logback/classic/issue/DarioCampagna/Main.java R logback-classic/src/test/java/ch/qos/logback/classic/issue/DarioCampagna/logback-marker.xml M logback-core/src/main/java/ch/qos/logback/core/joran/GenericConfigurator.java M logback-core/src/main/java/ch/qos/logback/core/joran/action/Action.java M logback-core/src/main/java/ch/qos/logback/core/joran/action/DefinePropertyAction.java M logback-core/src/main/java/ch/qos/logback/core/model/processor/DefaultProcessor.java M logback-core/src/test/java/ch/qos/logback/core/joran/SimpleConfigurator.java M logback-core/src/test/java/ch/qos/logback/core/joran/action/IncludeActionTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/action/PropertyActionTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/conditional/IfThenElseTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitConfigurationTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitConfigurator.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitFactory.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitFactoryAction.java Log Message: ----------- ongoing work Commit: 938e5f7137eb22326dd74b1a09736fac62271d87 https://github.com/qos-ch/logback/commit/938e5f7137eb22326dd74b1a09736fac62… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-09-26 (Wed, 26 Sep 2018) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/joran/GenericConfigurator.java M logback-core/src/test/java/ch/qos/logback/core/joran/SkippingInInterpreterTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/TrivialConfiguratorTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/action/TopElementAction.java M logback-core/src/test/java/ch/qos/logback/core/joran/conditional/IfThenElseAndIncludeCompositionTest.java M logback-core/src/test/java/ch/qos/logback/core/joran/event/ListenAction.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitConfigurator.java M logback-core/src/test/java/ch/qos/logback/core/joran/replay/FruitFactory.java M pom.xml Log Message: ----------- ongoign work on model based configuration Compare: https://github.com/qos-ch/logback/compare/72082076ed15...938e5f7137eb **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.

1 0

[JIRA] (LOGBACK-1427) JMS Queue Appender
by QOS.CH (JIRA) 26 Sep '18

26 Sep '18

Sudhik created LOGBACK-1427: ------------------------------- Summary: JMS Queue Appender Key: LOGBACK-1427 URL: https://jira.qos.ch/browse/LOGBACK-1427 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.1 Reporter: Sudhik Assignee: Logback dev list I'm using JMS Queue Appender of logback and seems like I'm getting below error after the first log is sent to queue. MQJCA1021: The message producer is closed. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Release Announcement: General Availability of JDK 11
by Rory O'Donnell 26 Sep '18

26 Sep '18

Hi Ceki, *1) Release Announcement: General Availability of JDK 11 * * JDK 11, the reference implementation of Java 11 and the first long-term support release produced under the six-month rapid-cadence release model [1][2], is now Generally Available. * GPL-licensed OpenJDK builds from Oracle are available here: https://jdk.java.net/11 This release includes seventeen features: * 181: Nest-Based Access Control <http://openjdk.java.net/jeps/181> * 309: Dynamic Class-File Constants <http://openjdk.java.net/jeps/309> * 315: Improve Aarch64 Intrinsics <http://openjdk.java.net/jeps/315> * 318: Epsilon: A No-Op Garbage Collector <http://openjdk.java.net/jeps/318> * 320: Remove the Java EE and CORBA Modules <http://openjdk.java.net/jeps/320> * 321: HTTP Client (Standard) <http://openjdk.java.net/jeps/321> * 323: Local-Variable Syntax for Lambda Parameters <http://openjdk.java.net/jeps/323> * 324: Key Agreement with Curve25519 and Curve448 <http://openjdk.java.net/jeps/324> * 327: Unicode 10 <http://openjdk.java.net/jeps/327> * 328: Flight Recorder <http://openjdk.java.net/jeps/328> * 329: ChaCha20 and Poly1305 Cryptographic Algorithms <http://openjdk.java.net/jeps/329> * 330: Launch Single-File Source-Code Programs <http://openjdk.java.net/jeps/330> * 331: Low-Overhead Heap Profiling <http://openjdk.java.net/jeps/331> * 332: Transport Layer Security (TLS) 1.3 <http://openjdk.java.net/jeps/332> * 333: ZGC: A Scalable Low-Latency Garbage Collector (Experimental) <http://openjdk.java.net/jeps/333> * 335: Deprecate the Nashorn JavaScript Engine <http://openjdk.java.net/jeps/335> * 336: Deprecate the Pack200 Tools and API <http://openjdk.java.net/jeps/336> 2) Quality Outreach Report for September 2018 is available* * * Quality Outreach report September 2018 *Thanks to everyone who contributed to JDK 11 by downloading and testing the early-access builds. In particular the following developers who logged **18 issues in the JDK Bug System.* * Netty * Eclipse Jetty * Apache Lucene * JUnit5 * Apache Tomcat * Apache Ant * Apache POI * AssertJ * Eclipse Collections * Byte Buddy * RxJava 3) JDK 12 EA build 12, under both the GPL and Oracle EA licenses, are now available at http://jdk.java.net/11 . * Schedule , Status & Features o http://openjdk.java.net/projects/jdk/12/ * Release Notes: o http://jdk.java.net/12/release-notes ** Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland

1 0

[JIRA] (LOGBACK-1426) JMS Queue Appender
by QOS.CH (JIRA) 25 Sep '18

25 Sep '18

1 0

[JIRA] (LOGBACK-1426) JMS Queue Appender
by QOS.CH (JIRA) 25 Sep '18

25 Sep '18

1 0

[JIRA] (LOGBACK-1426) JMS Queue Appender
by QOS.CH (JIRA) 25 Sep '18

25 Sep '18

1 0