- logback-dev - mailman3.qos.ch

JDK 12: First Release Candidate available
by Rory O'Donnell 18 Feb '19

18 Feb '19

Hi Ceki, **OpenJDK builds *- JDK 12 Early Access build 32 **is now available **at : - jdk.java.net/12/* **JDK 12: First Release Candidate [1]** * Per the JDK 12 schedule [2], we are now in Release Candidate Phase. * The stabilization repository, jdk/jdk12, is open for P1 bug fixes per the JDK Release Process (JEP 3) [3]. * All changes require approval via the Fix-Request Process [4]. * Release note additions since last email o Build 31 - can_pop_frame and can_force_early_return capabilities are disabled if JVMCI compiler is used (JDK-8218025 <https://bugs.openjdk.java.net/browse/JDK-8218025>) The JVMTI |can_pop_frame| and |can_force_early_return| capabilities are disabled if a JVMCI compiler (like Graal) is used. As a result the corresponding functionality (|PopFrame| and |ForceEarlyReturnXXX| functions) is not available to JVMTI agents. This issue is being fixed via JDK-8218885 <https://bugs.openjdk.java.net/browse/JDK-8218885> [https://bugs.openjdk.java.net/browse/JDK-8218885 <https://bugs.openjdk.java.net/browse/JDK-8218885>]. o Build 28: JDK-8212233 <https://bugs.openjdk.java.net/browse/JDK-8212233> : javadoc fails on jdk12 with "The code being documented uses modules but the packages defined in $URL are in the unnamed module." * Changes in this build. <http://hg.openjdk.java.net/jdk/jdk12/log?rev=reverse%28%22jdk-12%2B31%22%3A…> **OpenJDK builds *- JDK 13 Early Access build 8 is **now available **at : - jdk.java.net/13/* * These early-access, open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release Notes updates * Build 8 o GraphicsEnvironment.getCenterPoint()/getMaximumWindowBounds() are unified across the platforms (JDK-8214918 <https://bugs.openjdk.java.net/browse/JDK-8214918>) o The experimental FIPS 140 compliant mode has been removed from the SunJSSE provider. (JDK-8217835 <https://bugs.openjdk.java.net/browse/JDK-8217835>) * Build 7 o Change DOM parser to not resolve EntityReference and add Text node with DocumentBuilderFactory.setExpandEntityReferences(false) (JDK-8206132 <https://bugs.openjdk.java.net/browse/JDK-8206132>) * Build 6 o Base64.Encoder and Base64.Decoder methods can throw OutOfMemoryError (JDK-8210583 <https://bugs.openjdk.java.net/browse/JDK-8210583>) * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B7%22%3A%3A…> * FOSS Bugs fixed in recent builds o Build 6 : JDK-8216970 <https://bugs.openjdk.java.net/browse/JDK-8216970> : condy causes JVM crash o Build 7: JDK-8215577 <https://bugs.openjdk.java.net/browse/JDK-8215577> : Remove javadoc support for HTML 4 Rgds,Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-February/002623.html [2] http://openjdk.java.net/projects/jdk/12/#Schedule [3] http://openjdk.java.net/jeps/3 [4] http://openjdk.java.net/jeps/3#Fix-Request-Process -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1374) Increase timestamp resolution
by QOS.CH (JIRA) 12 Feb '19

12 Feb '19

1 0

[JIRA] (LOGBACK-1374) Increase timestamp resolution
by QOS.CH (JIRA) 11 Feb '19

11 Feb '19

1 0

[JIRA] (LOGBACK-1457) Avoid instantiating unused appenders
by QOS.CH (JIRA) 06 Feb '19

06 Feb '19

1 0

[JIRA] (LOGBACK-1457) Avoid instantiating unused appenders
by QOS.CH (JIRA) 06 Feb '19

06 Feb '19

Gili created LOGBACK-1457: ----------------------------- Summary: Avoid instantiating unused appenders Key: LOGBACK-1457 URL: https://jira.qos.ch/browse/LOGBACK-1457 Project: logback Issue Type: Improvement Components: logback-core Affects Versions: 1.2.3 Environment: If {{logback.xml}} contains a FILE appenders, but the parent directories cannot be created then we get a runtime exception. Example: {code:java} 18:49:04,076 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - openFile(null,true) call failed. java.io.FileNotFoundException: log/auction-house-cluster.2019-02-06.log (No such file or directory) at java.io.FileNotFoundException: log/auction-house-cluster.2019-02-06.log (No such file or directory) at java.base/java.io.FileOutputStream.open0(Native Method) at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298) at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:237) at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:26) at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:204) at ch.qos.logback.core.FileAppender.start(FileAppender.java:127) at ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:100) at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:90) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:309) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:193) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:179) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:165) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:152) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383) at com.company.Testcase.<clinit>(Testcase.java:16) {code} However, when we run under Docker we want to keep the appender definition in place but direct output to STDOUT instead. The problem is that Logback initializes the appender even when it isn't in use, consequently we get an error even when nothing is wrong. There are workarounds, such as conditional blocks, but reduce the readability of the configuration file. Please avoid initializing unused appenders. Reporter: Gili Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1456) Update Java EE dependencies
by QOS.CH (JIRA) 30 Jan '19

30 Jan '19

Gili created LOGBACK-1456: ----------------------------- Summary: Update Java EE dependencies Key: LOGBACK-1456 URL: https://jira.qos.ch/browse/LOGBACK-1456 Project: logback Issue Type: Improvement Components: logback-access Affects Versions: 1.3.0-alpha4 Reporter: Gili Assignee: Logback dev list Please update all Java EE dependencies per [https://wiki.eclipse.org/New_Maven_Coordinates] otherwise users who depend on slf4j and logback will be unable to update the dependencies on their end. For example, if you depend on the old coordinates and someone attempts to "upgrade" the dependency version by depending on the new coordinates with the higher version number then both versions (with the old and new coordinates) will get pulled in as dependencies. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1194) scanPeriod attribute is required by logback-classic for auto-reload to work
by QOS.CH (JIRA) 28 Jan '19

28 Jan '19

1 0

[JIRA] (LOGBACK-1303) Wrong delimiter in pattern layout for ISO 8601
by QOS.CH (JIRA) 27 Jan '19

27 Jan '19

1 0

[JIRA] (LOGBACK-1455) When log file index is greater than 1000, the old files will no longger be deleted
by QOS.CH (JIRA) 27 Jan '19

27 Jan '19

Raven created LOGBACK-1455: ------------------------------ Summary: When log file index is greater than 1000, the old files will no longger be deleted Key: LOGBACK-1455 URL: https://jira.qos.ch/browse/LOGBACK-1455 Project: logback Issue Type: Bug Reporter: Raven Assignee: Logback dev list My config file just like this: {color:#e8bf6a}<appender {color}{color:#bababa}name{color}{color:#e6db74}="FILE_VERBOSE" {color}{color:#bababa}class{color}{color:#e6db74}="ch.qos.logback.core.rolling.RollingFileAppender"{color}{color:#e8bf6a}> {color}{color:#e8bf6a} <file>{color}$\{LOG_HOME}/app.log{color:#e8bf6a}</file> {color}{color:#e8bf6a} <encoder> {color}{color:#e8bf6a} <charset>{color}UTF-8{color:#e8bf6a}</charset> {color}{color:#e8bf6a} <pattern>{color}%d\{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger\{36} - %msg%n{color:#e8bf6a}</pattern> {color}{color:#e8bf6a} </encoder> {color}{color:#e8bf6a} <rollingPolicy {color}{color:#bababa}class{color}{color:#e6db74}="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"{color}{color:#e8bf6a}> {color}{color:#e8bf6a} <fileNamePattern>{color}$\{LOG_HOME}/app.%d\{yyyy-MM-dd}.%i.log{color:#e8bf6a}</fileNamePattern> {color}{color:#e8bf6a} <maxHistory>{color}5{color:#e8bf6a}</maxHistory> {color}{color:#e8bf6a} <totalSizeCap>{color}100MB{color:#e8bf6a}</totalSizeCap> {color}{color:#e8bf6a} <timeBasedFileNamingAndTriggeringPolicy {color}{color:#bababa}class{color}{color:#e6db74}="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"{color}{color:#e8bf6a}> {color}{color:#e8bf6a} <maxFileSize>{color}10MB{color:#e8bf6a}</maxFileSize> {color}{color:#e8bf6a} </timeBasedFileNamingAndTriggeringPolicy> {color}{color:#e8bf6a} </rollingPolicy> {color}{color:#e8bf6a}</appender>{color} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-793) Logback RollingFileAppender error when trying to do manual rollover
by QOS.CH (JIRA) 21 Jan '19

21 Jan '19

1 0