March 2020 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 31 Mar '20

31 Mar '20

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 30 Mar '20

30 Mar '20

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 30 Mar '20

30 Mar '20

1 0

[JIRA] (LOGBACK-1513) Add possibity for separate logging for JPMS module/layers
by QOS.CH (JIRA) 29 Mar '20

29 Mar '20

Pavel_K created LOGBACK-1513: -------------------------------- Summary: Add possibity for separate logging for JPMS module/layers Key: LOGBACK-1513 URL: https://jira.qos.ch/browse/LOGBACK-1513 Project: logback Issue Type: New Feature Environment: I suggest to add possibility for separate logging for JPMS module/layers. For example, it would be possible to route messages from different modules/layers to separate log files. Reporter: Pavel_K Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1512) let SCHEDULED_EXECUTOR_POOL_SIZE be configurable
by QOS.CH (JIRA) 26 Mar '20

26 Mar '20

Liang Xie created LOGBACK-1512: ---------------------------------- Summary: let SCHEDULED_EXECUTOR_POOL_SIZE be configurable Key: LOGBACK-1512 URL: https://jira.qos.ch/browse/LOGBACK-1512 Project: logback Issue Type: Improvement Components: logback-classic, logback-core Affects Versions: 1.3.0-alpha5, 1.2.3, 1.1.11 Environment: AWS m5.xlarge ec2 instance, vCPU num: 4 Reporter: Liang Xie Assignee: Logback dev list Attachments: cpu_spike.png, latency.png Our log servers deployed logback component, the logback configuration contains tens of appenders, this is one of the appender definition: {quote}<appender name="rawdata" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/data/xxx/rawdata/rawdata.log</file> <encoder> <pattern>%m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/data/xxx/rawdata/rawdata.log.%d\{yyyy-MM-dd-HH}.gz</fileNamePattern> </rollingPolicy> </appender> {quote} please note the "fileNamePattern" value, we use gzip compression, it means in each hour beginning, all the tens of files are renamed to tmp files, then be compressed in the thread pool. Currently, this thread pool core size is immutable, a fixed value: 8, which came from [https://github.com/qos-ch/logback/commit/b946551439134] In an small ec2 env with tens of big log files(a few of our rolling raw log files size are 10 Gb), say 4 vcore, the compression will be last several minutes with all vcores running in full speed. It will disturb the normal user request latency espencially under a high throughput env. Our proposed solution are as following: 1. let SCHEDULED_EXECUTOR_POOL_SIZE be configurable, it is meaningful since the logback users have different cpu core configs, different requirements(latency vs throughput) 2. let the compression level be configurable, currently, the logback uses JDK's GZIPOutputStream class, which deflate algorithm is DEFAULT_COMPRESSION always. It would be great if we could make it be configurable. We forked a branch, after updating SCHEDULED_EXECUTOR_POOL_SIZE to 1 and deflate algorithm to BEST_SPEED, we have observed the each hour beginning's cpu spikes were relieved , and the user request latency is more stable than before Any comments are welcome -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Expired SSL certificates
by Mark Carroll 23 Mar '20

23 Mar '20

I'm guessing it is known that the webserver TLS certificates for https://logback.qos.ch/ and https://www.slf4j.org/ expired last week? Apologies if I missed the mailing list traffic or bug report for it or if this is the wrong place to mention the issue. -- Mark The University of Dundee is a registered Scottish Charity, No: SC015096

2 1

[JIRA] (LOGBACK-1510) logback is opening multiple files at the same time for same appender.
by QOS.CH (JIRA) 19 Mar '20

19 Mar '20

1 0

[JIRA] (LOGBACK-1424) high contention at ch.qos.logback.core.AsyncAppenderBase.putUninterruptibly
by QOS.CH (JIRA) 18 Mar '20

18 Mar '20

1 0

Release Announcement: General Availability of Java 14 / JDK 14
by Rory O'Donnell 18 Mar '20

18 Mar '20

Hi Ceki, **Release Announcement: General Availability of Java 14 / JDK 14 [1] * * * JDK 14, the reference implementation of Java 14, is now Generally Available. * GPL-licensed OpenJDK builds from Oracle are available here: https://jdk.java.net/14 * JDK 14 Release notes <https://www.oracle.com/technetwork/java/javase/14-relnote-issues-5809570.ht…> JDK 14 includes sixteen features [2]: 305: Pattern Matching for instanceof (Preview) 343: Packaging Tool (Incubator) 345: NUMA-Aware Memory Allocation for G1 349: JFR Event Streaming 352: Non-Volatile Mapped Byte Buffers 358: Helpful NullPointerExceptions 359: Records (Preview) 361: Switch Expressions (Standard) 362: Deprecate the Solaris and SPARC Ports 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector 364: ZGC on macOS 365: ZGC on Windows 366: Deprecate the ParallelScavenge + SerialOld GC Combination 367: Remove the Pack200 Tools and API 368: Text Blocks (Second Preview) 370: Foreign-Memory Access API (Incubator) Thanks to everyone who contributed to JDK 14, whether by creating features or enhancements, logging bugs, or downloading and testing the early-access builds. OpenJDK 15 EA build 14 is now available at http://jdk.java.net/15 * * * These early access, open source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Significant changes since the last availability email: o Build 13 - JDK-8238555 <https://bugs.openjdk.java.net/browse/JDK-8238555>: Allow Initialization of SunPKCS11 with NSS when there are external FIPS modules in the NSSDB o Build 10 - JDK-8237776 <https://bugs.openjdk.java.net/browse/JDK-8237776>: Shenandoah: Wrong result with Lucene test + Reported by Apache Lucene. o Build 9 - JDK-8222793 <https://bugs.openjdk.java.net/browse/JDK-8222793>: Javadoc tool ignores "-locale" param and uses default locale for all messages and texts + Reported by Apache Lucene. Project Metropolis Early-Access Builds - Build 14-metropolis+1-17 <http://jdk.java.net/metropolis/> (2020/3/5) * These builds are intended for developers looking to test and provide feedback on using /Graal,/ in form of native library /(libjvmcicompiler.so)/, instead of C2 as HotSpot high optimizing JIT compiler. * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Please send feedback via e-mail to metropolis-dev(a)openjdk.java.net <mailto:metropolis-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/metropolis-dev>. Regards, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2020-March/004089.html [2] https://openjdk.java.net/projects/jdk/14 -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (LOGBACK-1511) SizeAndTimeBasedRollingPolicy not honoring value of totalSizeCap
by QOS.CH (JIRA) 17 Mar '20

17 Mar '20

kalpesh bandi created LOGBACK-1511: -------------------------------------- Summary: SizeAndTimeBasedRollingPolicy not honoring value of totalSizeCap Key: LOGBACK-1511 URL: https://jira.qos.ch/browse/LOGBACK-1511 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: Linux 3.10.0-1062.12.1.el7.x86_64 x86_64 Reporter: kalpesh bandi Assignee: Logback dev list I am using "SizeAndTimeBasedRolling" policy. where below are the values <maxFileSize>100MB</maxFileSize> <maxHistory>4</maxHistory> <totalSizeCap>500MB</totalSizeCap> but it does not remove old file from past date. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0