August 2019 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1483) Headers are getting added during every application startup while configuring programmatically
by QOS.CH (JIRA) 31 Aug '19

31 Aug '19

Sai Srikar Mutya created LOGBACK-1483: ----------------------------------------- Summary: Headers are getting added during every application startup while configuring programmatically Key: LOGBACK-1483 URL: https://jira.qos.ch/browse/LOGBACK-1483 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Sai Srikar Mutya Assignee: Logback dev list Priority: Critical Use case : Application has to write events into a ".tmp" file and there is a time based rolling policy which rotates log file for every minute. Also, there is a header which needs to be appended for every log file. So I have used ` PatternLayoutEncoderBase` class to set headers and pattern. Problem: If I am restarting my application during the same minute, Headers are getting appended multiple times. So we need an option to not append the header if they are already present. I have also tried an option where we check the file during application startup, but there is a scenario where the application starts during a minute and the events are getting logged in the next minute. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1482) RollingFileAppender creates .tmp file while creating GZ file at midnight
by QOS.CH (JIRA) 29 Aug '19

29 Aug '19

Abhijit Kangale created LOGBACK-1482: ---------------------------------------- Summary: RollingFileAppender creates .tmp file while creating GZ file at midnight Key: LOGBACK-1482 URL: https://jira.qos.ch/browse/LOGBACK-1482 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha4 Environment: This is happening in production environment. Reporter: Abhijit Kangale Assignee: Logback dev list Priority: Critical Attachments: logback.xml After migrating our servers to openjdk11 we started observing this issue. We are using below configuration currently. We started using the latest versions of logback and slf4j. <version.java>11</version.java> <version.logback>1.3.0-alpha4</version.logback> <version.slf4j>1.8.0-beta4</version.slf4j> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>$\{version.logback}</version> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>log4j-over-slf4j</artifactId> <version>$\{version.slf4j}</version> <scope>runtime</scope> </dependency> We are using SizeAndTimeBasedRollingPolicy as rolling policy and rollover is set at midnight. Basically the roll over happens properly creating .gz file but at the same time it creates .tmp file for application log. -rw-r----- 1 iphsubmt iphsubmt 7805929 Aug 11 00:00 submissions-pipeline-metrics-2019-08-10.1.log.gz -rw-r----- 1 iphsubmt iphsubmt 8216 Aug 11 00:34 submissions-pipeline-dead-letters.log -rw-r----- 1 iphsubmt iphsubmt 14956341 Aug 11 14:33 submissions-pipeline-metrics-2019-08-11.0.log.gz -rw-r----- 1 iphsubmt iphsubmt 416634 Aug 12 00:00 submissions-pipeline-2019-08-11.0.log.gz *-rw-r----- 1 iphsubmt iphsubmt 13780 Aug 12 00:00 submissions-pipeline-2019-08-11.0.log2815836846996630.tmp* I have referred all open and closed tickets on this topic but nothing helped to resolve our issue. So please. I have attached logbook.xml file we are using. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1475) SyslogOutputStream ignores IP address changes for Syslog host
by QOS.CH (JIRA) 25 Aug '19

25 Aug '19

1 0

[JIRA] (LOGBACK-1475) SyslogOutputStream ignores IP address changes for Syslog host
by QOS.CH (JIRA) 24 Aug '19

24 Aug '19

1 0

JDK 13 is now in the Release Candidate Phase & JDK 14 build 11 is available.
by Rory O'Donnell 24 Aug '19

24 Aug '19

Hi Ceki, *JDK 13 is now in the Release Candidate Phase * Per the JDK 13 schedule [1], we are now in the Release Candidate phase. The stabilization repository, jdk/jdk13, is open for P1 bug fixes per the JDK Release Process (JEP 3) [2]. All changes require approval via the Fix-Request Process [3]. For more details, see Mark Reinhold's email to jdk-dev mailing list [4] * Milestone Schedule: o GAC - Aug 22, 2019 o GAR - Sept 5, 2019 o GA - Sept 17, 2019 **OpenJDK 14 *EA build 11 is now available at **http://jdk.java.net/14** * * 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>. * Release Notes o http://jdk.java.net/14/release-notes * JEPs targeted to JDK 14 o JEP 352 <http://openjdk.java.net/jeps/352> - Non-Volatile Mapped Byte Buffers * Significant changes since the last availability email: o Build 10 + 8226374: Restrict TLS signature schemes and named groups + 8227439: Turn off AOT by default o Build 11 + 8224974: Implement JEP 352 * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B10%22%3A%3…> *jpackage EA - **Build 1 (2019/8/20) * * This is an early access build of JEP 343: Packaging Tool <https://openjdk.java.net/jeps/343>, aimed at testing a prototype implementation of jpackage, which is a new tool for packaging self-contained Java applications along with a Java Runtime Environment. * Build 1 (2019/8/20) is now available http://jdk.java.net/jpackage/ * Please send feedback via e-mail to core-libs-dev(a)openjdk.java.net <mailto:core-libs-dev@openjdk.java.net> Regards, Rory [1] https://openjdk.java.net/projects/jdk/13/#Schedule [2] https://openjdk.java.net/jeps/3 [3] https://openjdk.java.net/jeps/3#Fix-Request-Process [4] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-August/003250.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1406) Seems all threads blocked
by QOS.CH (JIRA) 19 Aug '19

19 Aug '19

1 0

[JIRA] (LOGBACK-1406) Seems all threads blocked
by QOS.CH (JIRA) 18 Aug '19

18 Aug '19

1 0

[JIRA] (LOGBACK-1481) When encoder pattern set as a variable then logback skips newline %n
by QOS.CH (JIRA) 18 Aug '19

18 Aug '19

Sergey Ponomarev created LOGBACK-1481: ----------------------------------------- Summary: When encoder pattern set as a variable then logback skips newline %n Key: LOGBACK-1481 URL: https://jira.qos.ch/browse/LOGBACK-1481 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: Linux Reporter: Sergey Ponomarev Assignee: Logback dev list Priority: Minor I have following logback.xml: {code} <?xml version="1.0" encoding="UTF-8"?> <configuration> <include resource="org/springframework/boot/logging/logback/defaults.xml"/> <property scope="context" name="pattern" value="%d{yyyy-MM-dd'T'HH:mm:ss.SSS'Z', UTC} ${LOG_LEVEL_PATTERN:-%5p} %logger [%t] $%X{trace}$ %X{loggingMessageExtender}: %m%n" /> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <Pattern>${pattern}</Pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="CONSOLE"/> </root> </configuration> {code} Then all log statements are written in the single line even given than the pattern have %n in the end -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1406) Seems all threads blocked
by QOS.CH (JIRA) 18 Aug '19

18 Aug '19

1 0

Question about backporting fixes
by Dan Groves 15 Aug '19

15 Aug '19

Hello, A product I work on has run into some logback log retention bugs which were fixed in LOGBACK-1361 and LOGBACK-1175. Both were fixed in 1.3.0-alpha1, which as I understand requires SLF4J 2.0.0 as SLF4J 1.8.0 is dead. The product has a dependency which requires SLF4J 1.7.x. There is a class, StaticLoggerBinder, which doesn't exist in 2.0.0, which this dependency needs. I've tried working around this, but have not found a solution that works for us. So I backported both LOGBACK-1361 and LOGBACK-1175. I forked the logback repository. I ported both changes into a branch off of branch_1.2.x. So far, everything seems to be working. I'd like to know if there is anything else I should backport and if that is the correct branch to use to build off of for a new 1.2.x logback build. thanks, Dan

1 0