May 2018 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1400) Let ResilientOutputStreamBase.openNewOutputStream() be override from outside the package
by QOS.CH (JIRA) 18 May '18

18 May '18

Peter Storch created LOGBACK-1400: ------------------------------------- Summary: Let ResilientOutputStreamBase.openNewOutputStream() be override from outside the package Key: LOGBACK-1400 URL: https://jira.qos.ch/browse/LOGBACK-1400 Project: logback Issue Type: Improvement Components: logback-core Affects Versions: 1.3.0-alpha4 Reporter: Peter Storch Assignee: Logback dev list Priority: Minor Let ResilientOutputStreamBase.openNewOutputStream() be override from outside the package. This method is currently package protected which means only subclasses in the same package can override this method. When other frameworks like Dropwizard want to provide their own implementation of a ResilientOutputStream they have to put their class in the ch.qos.logback.core.recovery package. Which causes a split package problem when using Java 9 modules: [https://github.com/dropwizard/dropwizard/issues/2312] If this method is meant to be overridden from outside logback-core, a "protected" modifier should be added. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Regarding logback help
by Md. Hasan Basri 17 May '18

17 May '18

Dear Concern, I'm a developer. One of my application is based on Jdk8, groovy 2.4 as language and on the top of Spring Framework. As a logger I'm using 'logback' dependencies. (*group: 'ch.qos.logback', name: 'logback-classic', version: '1.1.8'*). Basically, RollingFileAppender is working fine for me, But currently. For an example, Suppose the specific logger function is invoked at *2018-05-16 11:08:50*, A record entered into error.log and no rolling file is created. Well, when the next execution occurs approximately after 6 minutes at *2018-05-16 11:15:05*, A fresh file is created *error.2018-05-16-11-08.log* and *error.log* file is refreshed with only the new message. This behavior is as per the documentation. But currently, I'm in need of instant creation of log file as soon as the rolling complete. In that case, the new file *error.2018-05-16-11-08.log* which is created actually at *2018-05-16 11:15:05*, I need to create the same file actually at *2018-05-16 11:09:00* (means as soon as the minute based rolling is complete). <appender name="ERROR_LOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>logs/error.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>logs/error_log/error.%d{yyyy-MM-dd-HH-mm}.log </fileNamePattern> <maxHistory>10</maxHistory> </rollingPolicy> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS}\t%msg%n</pattern> </encoder> </appender> Through my investigation, The purpose is partially resolved by removing the below property. <file>logs/error.log</file> But, I also need to produce "/logs/error.log" file. So, is there any way to satisfy my first criteria without impacting error.log file. Please, feel free to ask me anything regarding this issue. Best Regards, Md. Hasan Basri

1 0

[JIRA] (LOGBACK-1399) Percentage char in fileNamePattern in FixedWindowRollingPolicy
by QOS.CH (JIRA) 11 May '18

11 May '18

Vitaliy created LOGBACK-1399: -------------------------------- Summary: Percentage char in fileNamePattern in FixedWindowRollingPolicy Key: LOGBACK-1399 URL: https://jira.qos.ch/browse/LOGBACK-1399 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.1 Reporter: Vitaliy Assignee: Logback dev list I could not use fileNamePattern with the percentage charge in directory name. Example: {code:java} <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>2</maxIndex> <FileNamePattern>dev%fzp/file.log.%i</FileNamePattern> </rollingPolicy> {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 11 Early Access build 12 available
by Rory O'Donnell 08 May '18

08 May '18

Hi Ceki, **JDK 11 EA build 12 , *****under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. ** * * Newly approved Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes * Summary of changes o https://download.java.net/java/early_access/jdk11/12/jdk-11+12.html *Notable changes in JDK 11 EA builds since last email:* * Build 11 - see Release Notes for details. o JDK-8201315 : SelectableChannel.register may be invoked while a selection operation is in progress * Build 10 - see Release Notes for details. o JDK-8200149 : Removal of "com.sun.awt.AWTUtilities" class o JDK-8189997 (not public) : Enhanced KeyStore Mechanisms o JDK-8175075 (not public) : 3DES Cipher Suites Disabled * Build 9: - see Release Notes for details. o JDK-8200152 : KerberosString uses UTF-8 encoding by default o JDK-8200458 : Readiness information previously recorded in SelectionKey ready set not preserved ** *Draft JEP: Deprecate pack200, unpack200 tools and related APIs. [1] * This draft JEP [2] proposes to deprecate the pack200 APIs and tools in the JDK. As outlined in the JEP, the usefulness of this technology have diminishing returns, the components using them are being removed and connectivity speeds have improved by leaps and bounds, since its inception. Feedback appreciated via http://mail.openjdk.java.net/pipermail/jdk-dev Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001074.html [2] https://bugs.openjdk.java.net/browse/JDK-8200752 Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland

1 0

[JIRA] (LOGBACK-891) Deadlock in RollingFileAppender
by QOS.CH (JIRA) 04 May '18

04 May '18

1 0

[JIRA] (LOGBACK-891) Deadlock in RollingFileAppender
by QOS.CH (JIRA) 01 May '18

01 May '18

1 0

[JIRA] (LOGBACK-1398) This is my configuration, but the log to 980 is invalid.
by QOS.CH (JIRA) 01 May '18

01 May '18

Alex created LOGBACK-1398: ----------------------------- Summary: This is my configuration, but the log to 980 is invalid. Key: LOGBACK-1398 URL: https://jira.qos.ch/browse/LOGBACK-1398 Project: logback Issue Type: Bug Reporter: Alex Assignee: Logback dev list Attachments: 微信截图_20180501190022.png, 微信截图_20180501190208.png This is my configuration, but the log to 980 is invalid. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0