- logback-dev - mailman3.qos.ch

JDK 12 Early Access build 15 is available
by Rory O'Donnell 15 Oct '18

15 Oct '18

Hi Ceki, *JDK 12 Early Access build 15 is available at : - jdk.java.net/12/* * JDK 12 Schedule is confirmed. o 2018/12/13 Rampdown Phase One <http://openjdk.java.net/jeps/3#rdp-1> o 2019/01/17 Rampdown Phase Two <http://openjdk.java.net/jeps/3#rdp-2> o 2019/02/07 Release-Candidate Phase <http://openjdk.java.net/jeps/3#rc> o 2019/03/19 General Availability * Release Notes for JDK 12 [1] * JEPs targeted to JDK 12, so far o 325: Switch Expressions (Preview [2]) - Integrated o 326: Raw String Literals (Preview [2]) - Integrated o 340: One AArch64 Port, Not Two <http://openjdk.java.net/jeps/340> - Targeted o 341: Default CDS Archives <http://openjdk.java.net/jeps/341>- Integrated * Important fixes since last email o (b15) Implementation of JEP 341: Default CDS Archives o (b14) LDAPS Communication Failure (JDK-8211107 <https://bugs.openjdk.java.net/browse/JDK-8211107>) o (b14) Support dns_canonicalize_hostname in krb5.conf (JDK-8210821 <https://bugs.openjdk.java.net/browse/JDK-8210821>) o (b14) Removal of com.sun.awt.SecurityWarning Class (JDK-8210692 <https://bugs.openjdk.java.net/browse/JDK-8210692>) *JDK 8u202 planning [3]* * 8u202 is proposed to be the last Oracle led release for this OpenJDK Project. * A proposed timeline is as follows : o July 2018 8u-dev forest begins collecting 8u202 fixes o Mid October 2018 RampDown 2 o Mid January 2019 GA Rgds, Rory [1] http://jdk.java.net/12/release-notes [2] http://openjdk.java.net/jeps/12 [3] http://mail.openjdk.java.net/pipermail/jdk8u-dev/2018-September/007923.html<http://jdk.java.net/12/release-notes> <https://download.java.net/java/early_access/jmc7/core/common/docs/api/overv…> -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-708) Color support and Eclipse console
by QOS.CH (JIRA) 12 Oct '18

12 Oct '18

1 0

[JIRA] (LOGBACK-1085) make output colorization optional
by QOS.CH (JIRA) 12 Oct '18

12 Oct '18

1 0

[JIRA] (LOGBACK-1430) heuristics to automatically disable ANSI color code is not supported
by QOS.CH (JIRA) 12 Oct '18

12 Oct '18

1 0

[JIRA] (LOGBACK-1430) heuristics to automatically disable ANSI color code is not supported
by QOS.CH (JIRA) 12 Oct '18

12 Oct '18

Simon created LOGBACK-1430: ------------------------------ Summary: heuristics to automatically disable ANSI color code is not supported Key: LOGBACK-1430 URL: https://jira.qos.ch/browse/LOGBACK-1430 Project: logback Issue Type: Improvement Environment: Reporter: Simon Assignee: Logback dev list Logback ConsoleAppender supports color output using ANSI code but some consoles does not support it well and so print some crappy characters (like [eclipse IDE console|https://bugs.eclipse.org/bugs/show_bug.cgi?id=112948] or some windows platform ): {code:java} [main] [34mINFO [0;39m [36mo.e.l.s.d.Server[0;39m - Web server started at http://0.0.0.0:8080/. {code} This makes this feature hard to use because you should accept to be ugly in some conditions to be pretty in others. The trade-off doesn't seem worthy. A solution could be to add some heuristic to know if logback should use ANSI code or not. You could have a look at the way picocli do it : [https://github.com/remkop/picocli/issues/512#issuecomment-429170587] If you're not so confident because you don't want to break behavior of ConsoleAppender, you could begin with an other ConsoleAppender. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

large no of AsyncAppender threads
by Jamie 12 Oct '18

12 Oct '18

Hi All How can we limit the no. of Async Appender threads in our multitenant app? Surely, these threads should run off a single thread pool? Legends Thread Group Count States _AsyncAppender-Worker_ <http://fastthread.io/same-state-threads.jsp?state=threadGroup&threadGroup=0…> *46*threads _AsyncAppender-Worker-trash_ <http://fastthread.io/same-state-threads.jsp?state=threadGroup&threadGroup=1…> *44*threads _AsyncAppender-Worker-audit_ <http://fastthread.io/same-state-threads.jsp?state=threadGroup&threadGroup=2…> *44*threads *WAITING:*44 threads (100%) Thanks Jamie

1 0

[JIRA] (LOGBACK-1429) MarkerFactory.getMarkert(..) doubles logger root, creates extra logger congext
by QOS.CH (JIRA) 11 Oct '18

11 Oct '18

Máté Kovács created LOGBACK-1429: ------------------------------------ Summary: MarkerFactory.getMarkert(..) doubles logger root, creates extra logger congext Key: LOGBACK-1429 URL: https://jira.qos.ch/browse/LOGBACK-1429 Project: logback Issue Type: Bug Components: logback-classic, logback-core Affects Versions: 1.3.0-alpha4 Environment: uname -a Linux mate-Latitude-5580 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux /usr/lib/jvm/java-1.11.0-openjdk-amd64/bin/java -version openjdk version "10.0.2" 2018-07-17 OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.2) OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.2, mixed mode) Command line running the code is: /usr/lib/jvm/java-1.11.0-openjdk-amd64/bin/java -javaagent:/home/mate/work/idea-IC-181.5281.24/lib/idea_rt.jar=45441:/home/mate/work/idea-IC-181.5281.24/bin -Dfile.encoding=UTF-8 -classpath /home/mate/work/trials/doubleLoggerRoot/out/production/doubleLoggerRoot:/home/mate/.m2/repository/ch/qos/logback/logback-classic/1.3.0-alpha4/logback-classic-1.3.0-alpha4.jar:/home/mate/.m2/repository/ch/qos/logback/logback-core/1.3.0-alpha4/logback-core-1.3.0-alpha4.jar:/home/mate/.m2/repository/org/slf4j/slf4j-api/1.8.0-beta1/slf4j-api-1.8.0-beta1.jar:/home/mate/.m2/repository/com/sun/mail/javax.mail/1.6.0/javax.mail-1.6.0.jar:/home/mate/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar hu.alerant.Main Reporter: Máté Kovács Assignee: Logback dev list Priority: Critical Calling MarkerFactory.getMarker("any marker") doubles the logger root, and the logger context. If you want to obtain loggers created before the marker using the factory, you will get new instances. Here is an example code: {code:java} import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.slf4j.Marker; import org.slf4j.MarkerFactory; public class Main { public static void main(String[] args) { Logger l1 = LoggerFactory.getLogger(Main.class); Logger l2 = LoggerFactory.getLogger(Main.class); if(l1==l2) { System.out.println("The first two loggers are the same"); } Marker newMarker = MarkerFactory.getMarker("NewMarker"); Logger l3 = LoggerFactory.getLogger(Main.class); if(l1==l3) { System.out.println("l1==l3"); } else { System.out.println("l1!=l3"); } } }{code} Here is the output on my machine: {noformat} The first two loggers are the same l1!=l3{noformat} The above code proves that you can obtain the same logger from the factory multiple times. However, after you instantiate a marker using the factory, you will get new instances instead of the old ones. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1428) class LogginEventVo may have a code misstake which leads to a zero timestamp and finnaly an incorrect time in log file
by QOS.CH (JIRA) 08 Oct '18

08 Oct '18

dengweiyi created LOGBACK-1428: ---------------------------------- Summary: class LogginEventVo may have a code misstake which leads to a zero timestamp and finnaly an incorrect time in log file Key: LOGBACK-1428 URL: https://jira.qos.ch/browse/LOGBACK-1428 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha4 Environment: macos sierra 10.12.6 Reporter: dengweiyi Assignee: Logback dev list Priority: Minor Attachments: bug-logback-snapshot1.png, bug-logback-snapshot2.png, bug-logback-snapshot3.png it's a small code misstake which could be saw in the attachment. because of this, timestamp of LogginEventVo will be zero. in my situation,i use SocketAppender and SimpleSocketServer to achieve the goal of remote log collection. when i do my test, the time in the log file at the server side is incorrect. the time is 1970-01-01 08:00:00.000. after researching, it turns out to be above problem. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[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