- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1416) cann't delete the history log base on periodtype hour after system start
by QOS.CH (JIRA) 25 Aug '18

25 Aug '18

yanwuhua created LOGBACK-1416: --------------------------------- Summary: cann't delete the history log base on periodtype hour after system start Key: LOGBACK-1416 URL: https://jira.qos.ch/browse/LOGBACK-1416 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: suse linux Reporter: yanwuhua Assignee: Logback dev list # log setting:<appender name="DebugAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>$\{loggerHome}/logs/$\{moduleName}/debug/$\{moduleName}_debug.log</file> <append>true</append> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <fileNamePattern>$\{loggerHome}/logs/$\{moduleName}/debug/$\{moduleName}_debug_%d\{{color:#d04437}yyyyMMddHH{color}}_%i.log</fileNamePattern> <maxHistory>2</maxHistory> {color:#d04437} <CleanHistoryOnStart>true</CleanHistoryOnStart>{color} <maxFileSize>100MB</maxFileSize> </rollingPolicy> <encoder charset="UTF-8"> <pattern>%d\{yyyy-MM-dd HH:mm:ss.SSS}|%-5level|[%thread]|%m%n%</pattern> </encoder> </appender> # after set the CleanhistoryOnStart to true, the history log cann't be deleted base on the rule. # debugging the code,find the issue :ch.qos.logback.core.rolling.helper.RollingCalendar public long periodBarriersCrossed(long start, long end) \{ 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; switch (periodicityType) \{ case TOP_OF_MILLISECOND: return diff; case TOP_OF_SECOND: return diff / MILLIS_IN_ONE_SECOND; case TOP_OF_MINUTE: return diff / MILLIS_IN_ONE_MINUTE; {color:#d04437}case TOP_OF_HOUR:{color} {color:#d04437} return (int) diff / MILLIS_IN_ONE_HOUR;{color} case TOP_OF_DAY: return diff / MILLIS_IN_ONE_DAY; case TOP_OF_WEEK: return diff / MILLIS_IN_ONE_WEEK; case TOP_OF_MONTH: return diffInMonths(start, end); default: throw new IllegalStateException("Unknown periodicity type."); } } the red color code will return the number below 0. because covert long to int . the value will be < 0. It's the reason why we cann't delete the history logs after system start -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1229) byte count for tomcat is wrong when transfer encoding is chunked
by QOS.CH (JIRA) 24 Aug '18

24 Aug '18

1 0

JDK 11: First Release Candidate available
by Rory O'Donnell 24 Aug '18

24 Aug '18

Hi Ceki, *JDK 11 build 28 is our first JDK 11 Release Candidate [1] * * JDK 11 Early Access build 28 is available at : - jdk.java.net/11/ *FOSS fixes in recent builds.* * Eclipse Jetty - JDK-8207177 <https://bugs.openjdk.java.net/browse/JDK-8207177> (b27) * Apache Tomcat -JDK-8208642 <https://bugs.openjdk.java.net/browse/JDK-8208642>(b27) * Netty - JDK-8207029 <https://bugs.openjdk.java.net/browse/JDK-8207029> (b23), JDK-8208166 <https://bugs.openjdk.java.net/browse/JDK-8208166> (b25) *JDK 12 Early Access build 8 is available at : - jdk.java.net/12/* * Release Notes for JDK 12 [2] * Changes in this build include o JDK-8208350 <https://bugs.openjdk.java.net/browse/JDK-8208350> - Disable all DES TLS cipher suites *OpenJFX Early-Access Build 24 is available at :-* *http://jdk.java.net/openjfx/* * This library is delivered as a set of modules, along with the native code needed to run JavaFX, that can be run using a JDK 10 <http://jdk.java.net/10/> build or a JDK 11 EA <http://jdk.java.net/11/> build. * This build is intended to allow application developers and OpenJFX contributors to test their applications with an unbundled, standalone JavaFX library. Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-August/001844.html <http://openjdk.java.net/projects/jdk/11/#Schedule> [2] http://jdk.java.net/12/release-notes -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-995) Standalone rollover gets exception
by QOS.CH (JIRA) 23 Aug '18

23 Aug '18

1 0

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

23 Aug '18

1 0

Compression of log files is omitted when application is stopped at rollover
by ch w 21 Aug '18

21 Aug '18

*Description:* There is a bug report <https://jira.qos.ch/browse/LOGBACK-914> 4 years ago. It's not fixed yet. It occurs to me now. This is my configuration: > <rollingPolicy > class="ch.qos.logback.core.rolling.MyTimeBasedRollingPolicy"> > > <fileNamePattern>${baseLogPath}/logs/app.%d{yyyy-MM-dd}.log.gz</fileNamePattern> > </rollingPolicy> The log file will roll and compress at midnight normally. but, the compression is omitted if the application is not running at rolling time . The application will restart manually at next day , but the elapsed log file will not be compressed. *Solution:* I have an idea and have put it into practice to fix this problem. I add a property, say compressElapsedPeriodFileOnStart , to TimeBasedRollingPolicy ,default true. It compress the elapsed period log file, as below : 1 calculate the rolling period 2. generate the elapsed period log file name 3. compress it It works well for me, there is a better way ? I will push a PR if no.

1 0

[JIRA] (LOGBACK-914) Compression of log files is omitted when application is stopped at rollover
by QOS.CH (JIRA) 21 Aug '18

21 Aug '18

1 0

[JIRA] (LOGBACK-316) Netty Support
by QOS.CH (JIRA) 17 Aug '18

17 Aug '18

1 0

Logback Continuous Integration Smell Report
by Carmine Vassallo 15 Aug '18

15 Aug '18

Dear Logback developers, I’m Carmine, a researcher at the University of Zurich and I am interested in supporting developers working with continuous integration (CI). I created a reporting tool that analyzes the CI logs of a project to identify deviations from accepted CI best practices. For example, are you aware that the “configModel” branch has not been synchronized for 26 weeks, although in your project branches do typically not deviate for more than 3.86 weeks? You will find this and other interesting statistics about the CI practices in your project at https://carminevassallo.github.io/detectorsIcons/summarizer-output/qos-ch_l… . I would really appreciate if you could find the time to give me some feedback on the report that I generated for you or on my tool. Please fill out the following survey http://www.surveygizmo.com/s3/4515476/Summarizing-the-Continuous-Integratio… It usually takes 7 minutes (10 minutes at maximum). As a little encouragement, we will raffle of a 50$ Amazon voucher among all participants. If you have questions, please comment on this post or send an email at the address you’ll find in the survey. Thank you for your time! Best, Carmine.

1 0

[JIRA] (LOGBACK-1326) Allow LayoutWrappingEncoder to have a parent of a type other than Appender
by QOS.CH (JIRA) 15 Aug '18

15 Aug '18

1 0