September 2021 - logback-dev

[JIRA] Updates for LOGBACK-1579: Hourly rolling policy not working
by QOS.CH (JIRA) 30 Sep '21

30 Sep '21

logback / LOGBACK-1579 [Open] Hourly rolling policy not working ============================== 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-1579 ============================== Issue created ------------------------------ BATICLE created this issue on 30/Sep/21 10:28 PM Summary: Hourly rolling policy not working Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Components: logback-core Created: 30/Sep/21 10:28 PM Environment: Intellij / JDK 11 / Spring Boot 2.2.4 using logback 1.2.3 <appender name="TechFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${LOG_DIR}/test-app.%d{yyyy-MM-dd_HH}.log</fileNamePattern> <maxHistory>10</maxHistory> <cleanHistoryOnStart>true</cleanHistoryOnStart> </rollingPolicy> <encoder> <pattern>%d{yyyyMMdd.HHmmss}.%p.%t.%logger{35} %-5level - %msg %n</pattern> </encoder> </appender> Labels: TimeBasedRollingPolicy rollingPolicy Priority: Major Reporter: BATICLE Description: Hello, Figured out a bug inside class RollingCalendar in method "periodBarriersCrossed" when applying periodicityType = TOP_OF_HOUR. The "int cast" is applied to "diff" value making the resulting long value negative and not properly applying period calculation for the kind of periodicity. Fix is to delete the int cast. Workaround is creating all set of classes allowing us to override the default implementation of this RollingCalendar. <appender name="TechFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="CustomTimeBasedRollingPolicy"> <fileNamePattern>${LOG_DIR}/test-app.%d{yyyy-MM-dd_HH}.log</fileNamePattern> <maxHistory>10</maxHistory> <cleanHistoryOnStart>true</cleanHistoryOnStart> </rollingPolicy> <encoder> <pattern>%d{yyyyMMdd.HHmmss}.%p.%t.%logger{35} %-5level - %msg %n</pattern> </encoder> </appender> public class CustomTimeBasedRollingPolicy<E> extends TimeBasedRollingPolicy<E> { @Override public void start() { setTimeBasedFileNamingAndTriggeringPolicy(new CustomTimeBasedFileNamingAndTriggeringPolicy<>()); super.start(); } } class CustomTimeBasedFileNamingAndTriggeringPolicy<E> extends TimeBasedFileNamingAndTriggeringPolicyBase<E> { private static final String COLLIDING_DATE_FORMAT_URL = CODES_URL + "#rfa_collision_in_dateFormat"; private FileNamePattern fileNamePatternWithoutCompSuffix; @Override public void start() { super.start(); if (!super.isErrorFree()) return; final var fileNamePatternStr = tbrp.getFileNamePattern(); final var fileNamePattern = new FileNamePattern(fileNamePatternStr, this.context); fileNamePatternWithoutCompSuffix = new FileNamePattern(Compressor.computeFileNameStrWithoutCompSuffix(fileNamePatternStr, tbrp.getCompressionMode()), this.context); DateTokenConverter<Object> dtc = fileNamePattern.getPrimaryDateTokenConverter(); if (dtc == null) { throw new IllegalStateException("FileNamePattern [" + fileNamePattern.getPattern() + "] does not contain a valid DateToken"); } if (dtc.getTimeZone() != null) { rc = new CustomTopOfHourRollingCalendar(dtc.getDatePattern(), dtc.getTimeZone(), Locale.getDefault()); } else { rc = new CustomTopOfHourRollingCalendar(dtc.getDatePattern()); } addInfo("The date pattern is '" + dtc.getDatePattern() + "' from file name pattern '" + fileNamePattern.getPattern() + "'."); rc.printPeriodicity(this); if (!rc.isCollisionFree()) { addError("The date format in FileNamePattern will result in collisions in the names of archived log files."); addError(CoreConstants.MORE_INFO_PREFIX + COLLIDING_DATE_FORMAT_URL); withErrors(); return; } if(fileNamePattern.hasIntegerTokenCOnverter()) { addError("Filename pattern ["+fileNamePattern+"] contains an integer token converter, i.e. %i, INCOMPATIBLE with this configuration. Remove it."); return; } archiveRemover = new TimeBasedArchiveRemover(fileNamePattern, rc); archiveRemover.setContext(context); started = true; } @Override public boolean isTriggeringEvent(File activeFile, final E event) { long time = getCurrentTime(); if (time >= nextCheck) { Date dateOfElapsedPeriod = dateInCurrentPeriod; addInfo("Elapsed period: " + dateOfElapsedPeriod); elapsedPeriodsFileName = fileNamePatternWithoutCompSuffix.convert(dateOfElapsedPeriod); setDateInCurrentPeriod(time); computeNextCheck(); return true; } else { return false; } } } class CustomTopOfHourRollingCalendar extends RollingCalendar { private final PeriodicityType calculatedPeriodicityType; CustomTopOfHourRollingCalendar(String datePattern) { super(datePattern); this.calculatedPeriodicityType = computePeriodicityType(); } CustomTopOfHourRollingCalendar(String datePattern, TimeZone tz, Locale locale) { super(datePattern, tz, locale); this.calculatedPeriodicityType = computePeriodicityType(); } @Override public long periodBarriersCrossed(long start, long end) { if(TOP_OF_HOUR == calculatedPeriodicityType) { if (start > end) throw new IllegalArgumentException("Start cannot come before end"); long startFloored = getStartOfCurrentPeriodWithGMTOffsetCorrection(start, getTimeZone()); long endFloored = getStartOfCurrentPeriodWithGMTOffsetCorrection(end, getTimeZone()); long diff = endFloored - startFloored; return diff / MILLIS_IN_ONE_HOUR; } return super.periodBarriersCrossed(start, end); } } ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1577) javax.xml.parsers.ParserConfigurationException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported.
by QOS.CH (JIRA) 27 Sep '21

27 Sep '21

1 0

[qos-ch/logback] 7c3a11: update jar-plugin version
by Ceki Gulcu 26 Sep '21

26 Sep '21

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 7c3a1182ab80fc7afa61e9438ca27f3e8e8e5eea https://github.com/qos-ch/logback/commit/7c3a1182ab80fc7afa61e9438ca27f3e8e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2021-09-26 (Sun, 26 Sep 2021) Changed paths: M pom.xml Log Message: ----------- update jar-plugin version Signed-off-by: Ceki Gulcu <ceki(a)qos.ch>

1 0

[JIRA] (LOGBACK-1577) javax.xml.parsers.ParserConfigurationException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported.
by QOS.CH (JIRA) 23 Sep '21

23 Sep '21

1 0

[JIRA] Updates for LOGBACK-1578: Unable to use LevelChangePropagator in a modular application
by QOS.CH (JIRA) 22 Sep '21

22 Sep '21

logback / LOGBACK-1578 [Open] Unable to use LevelChangePropagator in a modular application ============================== 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-1578 ============================== Issue created ------------------------------ Iiro Nykänen created this issue on 22/Sep/21 9:19 PM Summary: Unable to use LevelChangePropagator in a modular application Issue Type: Bug Affects Versions: 1.3.0-alpha10 Assignee: Logback dev list Components: logback-classic Created: 22/Sep/21 9:19 PM Environment: JDK16 Priority: Major Reporter: Iiro Nykänen Description: Using LevelChangePropagator in Logback configuration causes the following exception in a modular application: {noformat} Exception in thread "main" java.lang.IllegalAccessError: class ch.qos.logback.classic.jul.LevelChangePropagator (in module ch.qos.logback.classic) cannot access class java.util.logging.LogManager (in module java.logging) because module ch.qos.logback.classic does not read module java.logging {noformat} I'm not sure how the multi-release system works exactly, but the java.logging module is not present currently in the [module-info|https://github.com/qos-ch/logback/blob/d7deb965489591bfa86ceb87…] file. As it only makes sense to require the module if the LevelChangePropagator is used (as far as I know, I don't believe the core of Logback Classic would require java.logging?), I'd imagine adding a *requires static java.logging* statement should be enough. There is an open [pull request|https://github.com/qos-ch/logback/pull/501] for this issue, but it features a plain requires statement which forces the requirement for all users whether they need it or not. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1577: javax.xml.parsers.ParserConfigurationException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported.
by QOS.CH (JIRA) 21 Sep '21

21 Sep '21

logback / LOGBACK-1577 [Open] javax.xml.parsers.ParserConfigurationException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported. ============================== 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-1577 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 21/Sep/21 5:20 PM Summary: javax.xml.parsers.ParserConfigurationException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported. Issue Type: Bug Assignee: Logback dev list Created: 21/Sep/21 5:20 PM Priority: Major Reporter: Ceki Gülcü Description: {code:java} {{code} {code:java} {code} Failed to auto configure default logger context Reported exception: ch.qos.logback.core.joran.spi.JoranException: Parser configuration error occurred at ch.qos.logback.core.joran.event.SaxEventRecorder.buildSaxParser(SaxEventRecorder.java:89) at ch.qos.logback.core.joran.event.SaxEventRecorder.recordEvents(SaxEventRecorder.java:57) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:151) 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:417) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:362) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:388) [cut] Caused by: javax.xml.parsers.ParserConfigurationException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported. at oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:272) at ch.qos.logback.core.joran.event.SaxEventRecorder.buildSaxParser(SaxEventRecorder.java:82) ... 83 more ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1576) Configuration reloading not working with + in path
by QOS.CH (JIRA) 21 Sep '21

21 Sep '21

1 0

[JIRA] (LOGBACK-1576) Configuration reloading not working with + in path
by QOS.CH (JIRA) 20 Sep '21

20 Sep '21

1 0

[JIRA] Updates for LOGBACK-1576: Configuration reloading not working with + in path
by QOS.CH (JIRA) 20 Sep '21

20 Sep '21

logback / LOGBACK-1576 [Open] Configuration reloading not working with + in path ============================== 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-1576 ============================== Issue created ------------------------------ Oliver Pfau created this issue on 20/Sep/21 12:52 PM Summary: Configuration reloading not working with + in path Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Created: 20/Sep/21 12:52 PM Environment: Windows 10 Priority: Minor Reporter: Oliver Pfau Description: I am starting my application specifying passing the path to the logbach.xml like this: "java -Dlogback.configurationFile=data/logback.xml -jar myapp.jar" In the absolute path to the logback.xml is a "+" character and it seems like with that "+" the configuration reloading with scan="true" and scanPeriod does not work. If I remove the plus it works. The part of my logback.xml: {code:java} <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="5 seconds" debug="true"> <statusListener class="ch.qos.logback.core.status.NopStatusListener"/>  <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>userdata/log/hmi.log</file> ... {code} Are there any restrictions existing for the path to the logback.xml? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Release Announcement: General Availability of Java 17 / JDK 17
by Rory O'Donnell 14 Sep '21

14 Sep '21

Hi Ceki, *Release Announcement: General Availability of Java 17 / JDK 17 * ** * JDK 17, the reference implementation of Java 17, is now Generally Available. [1] * GPL-licensed OpenJDK builds from Oracle are available here: https://jdk.java.net/17/ <https://jdk.java.net/17/> * JDK 17 Release notes <https://www.oracle.com/java/technologies/javase/17-relnotes.html> * Inside Java: The Arrival of Java 17! <https://inside.java/2021/09/14/the-arrival-of-java17/> *JDK 17 includes the following features [2]:* * JEP 306: Restore Always-Strict Floating-Point Semantics <https://openjdk.java.net/jeps/306> * JEP 356: Enhanced Pseudo-Random Number Generators <https://openjdk.java.net/jeps/356> * JEP 382: New macOS Rendering Pipeline <https://openjdk.java.net/jeps/382> * JEP 391: macOS/AArch64 Port <https://openjdk.java.net/jeps/391> * JEP 398: Deprecate the Applet API for Removal <https://openjdk.java.net/jeps/398> * JEP 403: Strongly Encapsulate JDK Internals <https://openjdk.java.net/jeps/403> * JEP 406: Pattern Matching for switch (Preview) <https://openjdk.java.net/jeps/406> * JEP 407: Remove RMI Activation <https://openjdk.java.net/jeps/407> * JEP 409: Sealed Classes <https://openjdk.java.net/jeps/409> * JEP 410: Remove the Experimental AOT and JIT Compiler <https://openjdk.java.net/jeps/410> * JEP 411: Deprecate the Security Manager for Removal <https://openjdk.java.net/jeps/411> * JEP 412: Foreign Function & Memory API (Incubator) <https://openjdk.java.net/jeps/412> * JEP 414: Vector API (Second Incubator) <https://openjdk.java.net/jeps/414> * JEP 415: Context-Specific Deserialization Filters <https://openjdk.java.net/jeps/415> *JDK 17 will be a long-term-support (LTS) release* from most vendors,including Oracle. If you’re upgrading from the previous LTS release,JDK 11, then you have many more JEPs to look forward to, summarized here: https://openjdk.java.net/jdk/17/jeps-since-jdk-11 <https://openjdk.java.net/jdk/17/jeps-since-jdk-11> Thanks to everyone who contributed to JDK 17, whether by creating features or enhancements, logging bugs, or downloading and testing the early-access builds. *OpenJDK 18 Early Access build 14 is now available at https://jdk.java.net/18/ <https://jdk.java.net/18/> * * These early access, open source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <https://openjdk.java.net/legal/gplv2+ce.html>. * JEPs targeted to JDK 18, so far: o JEP 400: UTF-8 by Default <https://openjdk.java.net/jeps/400> o JEP 413: Code Snippets in Java API Documentation <https://openjdk.java.net/jeps/413> * Release Notes are available at https://jdk.java.net/18/release-notes <https://jdk.java.net/18/release-notes> * Significant changes since the last availability email: o JDK-8271745: Fix Issues With the KW and KWP Modes of SunJCE Provider o JDK-8262186: Call X509KeyManager.chooseClientAlias once for all key types o JDK-8225083: Remove Google certificate that is expiring in December 2021 o JDK-8251329: Zip File System Provider Throws ZipException when entry name element contains "." or ".." o JDK-8225082: Remove IdenTrust certificate that is expiring in September 2021 o *Project Loom Early-Access Builds* * Build 18-loom+2-74 (2021/8/7) based on jdk-18+9 <https://github.com/openjdk/jdk/releases/tag/jdk-18%2B9> is available - https://jdk.java.net/loom/ <https://jdk.java.net/loom/> * These early access, open source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <https://openjdk.java.net/legal/gplv2+ce.html>. * Please send feedback via e-mail to loom-dev(a)openjdk.java.net <mailto:loom-dev@openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <https://mail.openjdk.java.net/mailman/listinfo/loom-dev>. Rgds,Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2021-September/006037.html [2] https://openjdk.java.net/projects/jdk/17/ <https://openjdk.java.net/projects/jdk/17/>

1 0