- logback-dev - mailman3.qos.ch

Release Announcement: General Availability of Java 15 / JDK 15
by Rory O'Donnell 15 Sep '20

15 Sep '20

Hi Ceki, **Release Announcement: General Availability of Java 15 / JDK 15 [1] ** * JDK 15, the reference implementation of Java 15, is now Generally Available. * GPL-licensed OpenJDK builds from Oracle are available here: http://jdk.java.net/15/ * JDK 15 Release notes <https://www.oracle.com/java/technologies/javase/15-relnote-issues.html> JDK 15 includes fourteen features [2]: * JEP 339: Edwards-Curve Digital Signature Algorithm (EdDSA) <http://openjdk.java.net/jeps/339> * JEP 360: Sealed Classes (Preview) <http://openjdk.java.net/jeps/360> * JEP 371: Hidden Classes <http://openjdk.java.net/jeps/371> * JEP 372: Remove the Nashorn JavaScript Engine <http://openjdk.java.net/jeps/372> * JEP 373: Reimplement the Legacy DatagramSocket API <https://openjdk.java.net/jeps/373> * JEP 374: Disable and Deprecate Biased Locking <http://openjdk.java.net/jeps/374> * JEP 375: Pattern Matching for instanceof (Second Preview) <https://openjdk.java.net/jeps/375> * JEP 377: ZGC: A Scalable Low-Latency Garbage Collector <http://openjdk.java.net/jeps/377> * JEP 378: Text Blocks <http://openjdk.java.net/jeps/378> * JEP 379: Shenandoah: A Low-Pause-Time Garbage Collector <https://openjdk.java.net/jeps/379> * JEP 381: Remove the Solaris and SPARC Ports <https://openjdk.java.net/jeps/381> * JEP 383: Foreign-Memory Access API (Second Incubator) <https://openjdk.java.net/jeps/383> * JEP 384: Records (Second Preview) <https://openjdk.java.net/jeps/384> * JEP 385: Deprecate RMI Activation for Removal <https://openjdk.java.net/jeps/385> Thanks to everyone who contributed to JDK 15, whether by creating features or enhancements, logging bugs, or downloading and testing the early-access builds. OpenJDK 16 Early Access build 15**is now available at http://jdk.java.net/16 * JEPs integrated to JDK 16: o JEP 347: Enable C++14 Language Features <https://openjdk.java.net/jeps/347> o JEP 357: Migrate from Mercurial to Git <https://openjdk.java.net/jeps/357> o JEP 369: Migrate to GitHub <https://openjdk.java.net/jeps/369> * Release Notes are available at http://jdk.java.net/16/release-notes ** * Significant changes since the last availability email: o Build 15 + JDK-8244090: public lookup should find public members of public exported types (Reported by Eclipse Jetty) + JDK-8250968: Symlinks attributes not preserved when using jarsigner on zip files o Build 14 + JDK-8189744: Deprecate the JDK-specific API for setting socket options, jdk.net.Sockets + JDK-8241003: Deprecate "denigrated" java.security.cert APIs that represent DNs as Principal or String objects + JDK-8245462: The default HttpClient implementation returns cancelable futures *__* Rgds,Rory  [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2020-September/004733.html [2] https://openjdk.java.net/projects/jdk/15/ -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] Updates for LOGBACK-1525: Gradle error when adding logback-classic
by QOS.CH (JIRA) 05 Sep '20

05 Sep '20

logback / LOGBACK-1525 [Open] Gradle error when adding logback-classic ============================== 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-1525 ============================== Issue created ------------------------------ NonSonoCazziTuoi created this issue on 06/Sep/20 12:55 AM Summary: Gradle error when adding logback-classic Issue Type: Bug Affects Versions: 1.3.0-alpha5 Assignee: Logback dev list Components: logback-classic Created: 06/Sep/20 12:55 AM Labels: gradle intellij Priority: Blocker Reporter: NonSonoCazziTuoi Description: I get all these errors [errors|[https://pastebin.com/5Rr7ZGM4] ] when I add implementation group: 'ch.qos.logback', name: 'logback-classic', version: '1.3.0-alpha5' to Gradle ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1175) FilenamePattern used to TimeBasedArchiveRemover is limited for 999 files
by QOS.CH (JIRA) 01 Sep '20

01 Sep '20

1 0

[JIRA] Updates for LOGBACK-1524: SyslogAppender does not send FQDN hostname
by QOS.CH (JIRA) 31 Aug '20

31 Aug '20

logback / LOGBACK-1524 [Open] SyslogAppender does not send FQDN hostname ============================== 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-1524 ============================== Issue created ------------------------------ Mats Adolfsson created this issue on 31/Aug/20 1:58 PM Summary: SyslogAppender does not send FQDN hostname Issue Type: Improvement Assignee: Logback dev list Components: logback-classic Created: 31/Aug/20 1:58 PM Environment: The SyslogAppender uses the SyslogStartConverter which only sends the hostname without domain name to the syslog server. To be able to differentiate between servers with the same name in different domains I propose to change getHostName() to getCanonicalHostName(). Priority: Minor Reporter: Mats Adolfsson ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Evaluator error - getting ch.qos.logback.classic.Level could not be found
by RAJESH SIRIPURAPUKANDALA 23 Aug '20

23 Aug '20

Team, I am facing one error with my evaluator filter. I included SLFJ-API(1.7.25), logback-core, logback-classic (1.2.3) jars. Also added janino jar (3.1.1). In my logback.xml file belowis what I wrote. <appender name="syslogappender" class="ch.qos.logback.classic.net.SyslogAppender"> <filter class=ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression> if (level == ERROR && formattedMessage.contains("NullPointerException") ) { return true; } return false; </expression> </evaluator> <onMismatch> NEUTRAL</onMismatch> <onMatch>ACCEPT</onMatch> </filter> </appender> and I amhaving sysloghost, facility and suffixpattern tags as well passed in the above appender. my logger for the above appender is <logger additiity=false level="INFO"> <appender-ref ref=" syslogappender> </logger> <root> <level value="INFO" /> <appender-ref ref="syslogappender" </root> with this above, Iam deploying my app to IBM Mainframe WAS server. During deployment I am getting below error. org.codehaus.commons.compiler.CompileException a class ch.qos.logback.classic.Level could not be found. Please help me how to correct this issue. Thanks.

1 0

[JIRA] (LOGBACK-204) file appender that rolls on startup
by QOS.CH (JIRA) 20 Aug '20

20 Aug '20

1 0

[JIRA] (LOGBACK-736) Logging stops when a context is restarted
by QOS.CH (JIRA) 19 Aug '20

19 Aug '20

1 0

[JIRA] Updates for LOGBACK-1523: Re-Introduce Groovy config support (Groovy Support for Java >= 9 works)
by QOS.CH (JIRA) 17 Aug '20

17 Aug '20

logback / LOGBACK-1523 [Open] Re-Introduce Groovy config support (Groovy Support for Java >= 9 works) ============================== 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-1523 ============================== Issue created ------------------------------ Robert Oschwald created this issue on 17/Aug/20 3:46 PM Summary: Re-Introduce Groovy config support (Groovy Support for Java >= 9 works) Issue Type: Improvement Assignee: Logback dev list Created: 17/Aug/20 3:46 PM Environment: Groovy supports Java >= 9 since versions 2.5.0 / 3.0.0. See [https://issues.apache.org/jira/browse/GROOVY-8471] So the commits to remove Groovy support should be reverted. See [https://github.com/qos-ch/logback/search?q=java+9&type=Commits] Priority: Major Reporter: Robert Oschwald ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[qos-ch/logback] bbc783: added Antonio Tomac to CLAs
by Ceki Gulcu 12 Aug '20

12 Aug '20

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: bbc783e6d68482abe8e7dff0d06708175e971b91 https://github.com/qos-ch/logback/commit/bbc783e6d68482abe8e7dff0d06708175e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2020-08-12 (Wed, 12 Aug 2020) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- added Antonio Tomac to CLAs

1 0

[JIRA] Updates for LOGBACK-1522: SocketAppender blocks ReconfigureOnChangeTask
by QOS.CH (JIRA) 11 Aug '20

11 Aug '20

logback / LOGBACK-1522 [Open] SocketAppender blocks ReconfigureOnChangeTask ============================== 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-1522 ============================== Issue created ------------------------------ Wolfgang Deifel created this issue on 11/Aug/20 1:42 PM Summary: SocketAppender blocks ReconfigureOnChangeTask Issue Type: Bug Affects Versions: 1.3.0-alpha4 Assignee: Logback dev list Components: logback-classic Created: 11/Aug/20 1:42 PM Environment: Windows 10 Pro Priority: Critical Reporter: Wolfgang Deifel Description: When logback.xml configures a scan period it starts a repeating thread ReconfigureOnChangeTask using context.getScheduledExecutorService(). When starting a SocketAppender it uses the same getContext().getScheduledExecutorService() (in AbstractSocketAppender) to run the background Thread. Unfortuntely, this scheduledExecutorService has only one thread in its core pool and cannot add additional workers. So when starting the socketAppender the ReconfigureOnChangeTask is blocked an will never check the configuration file for updates. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0