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

[JIRA] Updates for LOGBACK-1555: Logback-access %B is not 0 when HTTP status code is 204 No Content
by QOS.CH (JIRA) 30 Mar '21

30 Mar '21

logback / LOGBACK-1555 [Open] Logback-access %B is not 0 when HTTP status code is 204 No Content ============================== 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-1555 ============================== Issue created ------------------------------ Dongfeng Lu created this issue on 30/Mar/21 7:13 PM Summary: Logback-access %B is not 0 when HTTP status code is 204 No Content Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Attachments: rest.zip Components: logback-access Created: 30/Mar/21 7:13 PM Environment: Java 11, Gradle 6.8.3 Priority: Major Reporter: Dongfeng Lu Description: [https://tomcat.apache.org/tomcat-8.0-doc/config/valve.html] says {code:java} %b - Bytes sent, excluding HTTP headers, or '-' if zero %B - Bytes sent, excluding HTTP headers {code} That is, %B returns number 0, instead of '-' if content-length is 0. We expected the same behavior from logback-access. However, this does not seem to be the case. I created a simple Spring Boot project with only "spring-boot-starter-web" and "logback-access:1.2.3", with simple configuration for logback-access.xml. Related to the ticket LOGBACK-1554, I knew %b and %B works only for String object. I created 4 simple REST APIs, all returning String object, but with non-empty string, empty string, null string, and null string with HTTP 204 status code. {code:java} http://localhost:8080/string http://localhost:8080/empty http://localhost:8080/null http://localhost:8080/noContent {code} I configured the app to use both Tomcat Access log and Logback-access log, the corresponding results are Spring Boot Tomcat Access Log {code:java} 0:0:0:0:0:0:0:1 - - [30/Mar/2021:11:27:13 -0500] "GET /string HTTP/1.1" 200 6 6 8 0:0:0:0:0:0:0:1 - - [30/Mar/2021:11:27:15 -0500] "GET /empty HTTP/1.1" 200 - 0 1 0:0:0:0:0:0:0:1 - - [30/Mar/2021:11:27:16 -0500] "GET /null HTTP/1.1" 200 - 0 2 0:0:0:0:0:0:0:1 - - [30/Mar/2021:11:27:19 -0500] "GET /noContent HTTP/1.1" 204 - 0 1 {code} Logback-access Log {code:java} Logback-access 0:0:0:0:0:0:0:1 - - 30/Mar/2021:11:27:13 -0500 "GET /string HTTP/1.1" 200 6 6 8 Logback-access 0:0:0:0:0:0:0:1 - - 30/Mar/2021:11:27:15 -0500 "GET /empty HTTP/1.1" 200 0 0 1 Logback-access 0:0:0:0:0:0:0:1 - - 30/Mar/2021:11:27:16 -0500 "GET /null HTTP/1.1" 200 0 0 2 Logback-access 0:0:0:0:0:0:0:1 - - 30/Mar/2021:11:27:19 -0500 "GET /noContent HTTP/1.1" 204 - - 1 {code} You can see %B in Tomcat access log is 0 when HTTP status is 204. However, it is '-' in logback-access log. I attached my simple project for you to reproduce it. You can unzip it, and run "gradlew clean bootRun". Please let me know if any additional information is needed. Thanks. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1554: Logback-access %b is empty, most of time
by QOS.CH (JIRA) 26 Mar '21

26 Mar '21

logback / LOGBACK-1554 [Open] Logback-access %b is empty, most of time ============================== 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-1554 ============================== Issue created ------------------------------ Dongfeng Lu created this issue on 26/Mar/21 6:08 PM Summary: Logback-access %b is empty, most of time Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Attachments: rest.zip Components: logback-access Created: 26/Mar/21 6:08 PM Environment: Java 11, Gradle Priority: Major Reporter: Dongfeng Lu Description: Originally, we were trying to get Tomcat access log in JSON format. We followed the example in https://github.com/jochenchrist/spring-boot-access-logs-demo and everything seems to work well, except that we were not able to get response's content length. To narrow things down, I created a simple Spring Boot project with only "spring-boot-starter-web" and "logback-access:1.2.3" (No logstash here), with simple configuration for logback-access.xml. I created 4 simple REST APIs, started the app and ran the following 4 requests in browser. {code} http://localhost:8080/list http://localhost:8080/map http://localhost:8080/long http://localhost:8080/string {code} The browser displays the response correctly in JSON format. And in the console, the corresponding access log entries were {code} 0:0:0:0:0:0:0:1 - - 26/Mar/2021:11:04:34 -0500 "GET /list HTTP/1.1" 200 124 - - - 0:0:0:0:0:0:0:1 - - 26/Mar/2021:11:04:36 -0500 "GET /map HTTP/1.1" 200 13 - - - 0:0:0:0:0:0:0:1 - - 26/Mar/2021:11:04:37 -0500 "GET /long HTTP/1.1" 200 6 - - - 0:0:0:0:0:0:0:1 - - 26/Mar/2021:11:04:39 -0500 "GET /string HTTP/1.1" 200 6 6 6 6 {code} Following http://logback.qos.ch/manual/layouts.html, I tried all the conversion word for the content length, "%b", "%B", and "%bytesSent", and they all seem to work and generate the content length, but ONLY if the response return type is "String". They did NOT generate the content length for Map, List or even a Long object. I attached my simple project for you to reproduce it. You can unzip it, and run "gradlew clean bootRun". Please let me know if any additional information is needed. Thanks. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1553: Logs not getting zipped and growing in gbs taking diskspace
by QOS.CH (JIRA) 16 Mar '21

16 Mar '21

logback / LOGBACK-1553 [Open] Logs not getting zipped and growing in gbs taking diskspace ============================== 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-1553 ============================== Issue created ------------------------------ Ayyasamy Radhakrishnan created this issue on 17/Mar/21 12:45 AM Summary: Logs not getting zipped and growing in gbs taking diskspace Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Attachments: disk270.log Components: logback-classic, logback-core Created: 17/Mar/21 12:45 AM Environment: Windows Server 2016. We are using logback framework with the config on the info mode <configuration debug="true" scan="true" scanPeriod="30 seconds" ><configuration debug="true" scan="true" scanPeriod="30 seconds" > <shutdownHook class="ch.qos.logback.core.hook.DelayingShutdownHook"> <delay>10000</delay> </shutdownHook> <appender name="fileinfo" class="ch.qos.logback.classic.sift.SiftingAppender">   <discriminator> <key>fis.logfilename</key> <defaultValue>defaultlogger-${bluepumpkin.ProcessName}</defaultValue> </discriminator> <sift> <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${IMPACT360DATADIR}/Logs/Integration Server/${fis.logfilename}-logback.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${IMPACT360DATADIR}/Logs/Integration Server/zip/${fis.logfilename}-logback.%d\{yyyy-MM-dd-HH}.%i.log.zip</fileNamePattern>   <maxHistory>168</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>30MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>####[${fis.processname}]-[${user.name}] [%date\{yyyy-MM-dd HH:mm:ss.SSSZ}] [%level] [%thread] [%logger\{-2}] <##[\{user=${user.name}}]##> - %message%n</pattern> </encoder> </appender> </sift> </appender> <logger name="org.eclipse.jetty.server.HttpChannel" level="OFF"/> <logger name="org.eclipse.jetty.http.HttpGenerator" level="OFF"/> <logger name="org.eclipse.jetty.io.WriteFlusher" level="OFF"/> <logger name="org.eclipse.jetty.server.HttpOutput" level="OFF"/>  <logger name="com.bluepumpkin.bpxCommon.common.Base.StopWatch" level="OFF"/> <root level="INFO"> <appender-ref ref="fileinfo" /> <appender-ref ref="file" /> </root> </configuration> Labels: TimeBasedRollingPolicy Priority: Major Reporter: Ayyasamy Radhakrishnan Description: We have multiple jvms running.. they are supposed log the info. For some reason the log file is not getting zipped up and keep on growing for multiple days. Beyond the max size configured. Small sample attached from the 250MB file logs attached.. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Release Announcement: General Availability of Java 16 / JDK 16
by Rory O'Donnell 16 Mar '21

16 Mar '21

Hi Ceki, *Release Announcement: General Availability of Java 16 / JDK 16 * ** * JDK 16, the reference implementation of Java 16, is now Generally Available. [1] * GPL-licensed OpenJDK builds from Oracle are available here: http://jdk.java.net/16/ <http://jdk.java.net/16/> * JDK 16 Release notes <https://www.oracle.com/java/technologies/javase/16-relnotes.html> *JDK 16 includes the following features [2]:* * JEP 338:Vector API (Incubator) <https://openjdk.java.net/jeps/338> * JEP 347:Enable C++14 Language Features <https://openjdk.java.net/jeps/347> * JEP 357:Migrate from Mercurial to Git <https://openjdk.java.net/jeps/357> * JEP 369:Migrate to GitHub <https://openjdk.java.net/jeps/369> * JEP 376:ZGC: Concurrent Thread-Stack Processing <https://openjdk.java.net/jeps/376> * JEP 380:Unix-Domain Socket Channels <https://openjdk.java.net/jeps/380> * JEP 386:Alpine Linux Port <https://openjdk.java.net/jeps/386> * JEP 387:Elastic Metaspace <https://openjdk.java.net/jeps/387> * JEP 388:Windows/AArch64 Port <https://openjdk.java.net/jeps/388> * JEP 389:Foreign Linker API (Incubator) <https://openjdk.java.net/jeps/389> * JEP 390:Warnings for Value-Based Classes <https://openjdk.java.net/jeps/390> * JEP 392:Packaging Tool <https://openjdk.java.net/jeps/392> * JEP 393:Foreign-Memory Access API (Third Incubator) <https://openjdk.java.net/jeps/393> * JEP 394:Pattern Matching for instanceof <https://openjdk.java.net/jeps/394> * JEP 395:Records <https://openjdk.java.net/jeps/395> * JEP 396:Strongly Encapsulate JDK Internals by Default <https://openjdk.java.net/jeps/396> * JEP 397:Sealed Classes (Second Preview) <https://openjdk.java.net/jeps/397> Thanks to everyone who contributed to JDK 16, whether by creating features or enhancements, logging bugs, or downloading and testing the early-access builds. *OpenJDK 17 Early Access build 13 is now available at http://jdk.java.net/17 <http://jdk.java.net/17/> * ** * 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>. * JEPs targeted to JDK 17, so far: o JEP 356: Enhanced Pseudo-Random Number Generators <https://openjdk.java.net/jeps/356> * Release Notes are available at http://jdk.java.net/17/release-notes <http://jdk.java.net/17/release-notes> * Significant changes since the last availability email: o JDK-8259709: Disable SHA-1 XML Signatures (b13) o JDK-6323374: (coll) Optimize Collections.unmodifiable* and synchronized*(b13) o JDK-8139348: Deprecate 3DES and RC4 in Kerberos (b12) o JDK-8259662: Don't wrap SocketExceptions into SSLExceptions in SSLSocketImpl (b11) o JDK-8235139: Deprecate the socket impl factory mechanism(b10) o JDK-8225081: Remove Telia Company CA certificate expiring in April 2021(b9) *Project Lanai Early-Access Builds * * EA 10 Build 17-lanai+3-133 (2021/3/2) is available - http://jdk.java.net/lanai/ * 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>. *Project Loom Early-Access Builds* * Build 17-loom+4-174 (2021/3/12) is available - http://jdk.java.net/loom/ * 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>. *Project Panama Early-Access Builds * * Build 17-panama+2-51 (2021/2/12) is available - http://jdk.java.net/panama/ * 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>. Rgds,Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2021-March/005188.html [2] https://openjdk.java.net/projects/jdk/16/ <https://openjdk.java.net/projects/jdk/16/>

1 0

[JIRA] (LOGBACK-1454) StackOverflow error
by QOS.CH (JIRA) 05 Mar '21

05 Mar '21

1 0

[JIRA] (LOGBACK-1454) StackOverflow error
by QOS.CH (JIRA) 05 Mar '21

05 Mar '21

1 0