- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1420) Args array is double trimmed when passing more than one trailing throwable
by QOS.CH (JIRA) 08 Sep '18

08 Sep '18

1 0

[JIRA] (LOGBACK-1420) Args array is double trimmed when passing more than one trailing throwable
by QOS.CH (JIRA) 08 Sep '18

08 Sep '18

LI CHUANYI created LOGBACK-1420: ----------------------------------- Summary: Args array is double trimmed when passing more than one trailing throwable Key: LOGBACK-1420 URL: https://jira.qos.ch/browse/LOGBACK-1420 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha5 Environment: java version "10.0.2" Windows 10 / IDEA Reporter: LI CHUANYI Assignee: Logback dev list Priority: Minor When passing more than one trailing throwable: {code:java} Logger logger = LoggerFactory.getLogger(Main.class); logger.warn("Message1={}, message2={}.", new Exception("I'm ex1"), new Exception("I'm ex2"), new Exception("I'm ex3")); {code} Output: 12:28:09.687 [main] WARN ch.qos.logback.classic.Main - Message1=java.lang.Exception: I'm ex1, {color:#d04437}message2=\{}{color}. java.lang.Exception: I'm ex3 at ch.qos.logback.classic/ch.qos.logback.classic.Main.main(Main.java:10) The second exception is trimmed by MessageFormatter#arrayFormat(String, Object[]) in LoggingEvent#getFormattedMessage(), although throwable had been already extracted in constructor. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 12 & JMC 7.0.0 Early Access builds are available
by Rory O'Donnell 07 Sep '18

07 Sep '18

Hi Ceki, *JDK 11 build 28 is our first JDK 11 Release Candidate [1] * * JDK 11 build 28 is available at : - jdk.java.net/11/ *JDK 12 Early Access build 10 is available at : - jdk.java.net/12/* * Release Notes for JDK 12 [2] * *JEPs integrated to JDK 12:* o 325: Switch Expressions (Preview [3]) * *JEPs proposed to target JDK 12:* o 326: Raw String Literals (Preview [3]) *FOSS bug fixes in recent builds.* * Apache Ant - JDK-8209965<https://bugs.openjdk.java.net/browse/JDK-8209965>(b09) *Other important fixes in JDK 12* * Disabled all DES TLS Cipher Suites (JDK-8208350 <https://bugs.openjdk.java.net/browse/JDK-8208350>) o DES-based TLS cipher suites are considered obsolete and should no longer be used *JMC 7.0.0 Early Access build 04 is available at :- **http://jdk.java.net/jmc/* * Overview - summary [4] * These early-access, open-source builds are provided under the Universal Permissive License, version 1.0<https://opensource.org/licenses/UPL>. * Feedback via the http://bugreport.java.com/ o Be sure to include jmc application Build id from "Help" - "About JDK Mission Control". Rgds, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-August/001844.html [2] http://jdk.java.net/12/release-notes [3] http://openjdk.java.net/jeps/12<http://jdk.java.net/12/release-notes> [4] https://download.java.net/java/early_access/jmc7/core/common/docs/api/overv… -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1419) Deployment fails on TomEE 7.0.5 for logback-classic newer than 1.1.9
by QOS.CH (JIRA) 06 Sep '18

06 Sep '18

Christian Kalkhoff created LOGBACK-1419: ------------------------------------------- Summary: Deployment fails on TomEE 7.0.5 for logback-classic newer than 1.1.9 Key: LOGBACK-1419 URL: https://jira.qos.ch/browse/LOGBACK-1419 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.3, 1.1.11, 1.2.2, 1.2.1, 1.2.0, 1.1.10 Environment: Apache TomEE 7.0.5 Reporter: Christian Kalkhoff Assignee: Logback dev list All versions later than 1.1.9 fail to deploy in TomEE 7.0.5 (possibly earlier, not tested). It seems to be related to the META-INF/services/javax.servlet.ServletContainerInitializer file as it fails directly after discovery and throws a java.lang.NoClassDefFoundException for javax.servlet.ServletContainerInitializer, basically the same outcome as in LOGBACK-1265. Since I tried all versions newer than 1.1.9 it seems to to be related to the cause of LOGBACK-1265 (comment in META-INF/services/javax.servlet.ServletContainerInitializer). -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1312) Tomcat 8.5.14 reports stale thread created by Logback
by QOS.CH (JIRA) 06 Sep '18

06 Sep '18

1 0

[JIRA] (LOGBACK-1396) JVM fatal error with libzip.so
by QOS.CH (JIRA) 06 Sep '18

06 Sep '18

1 0

[JIRA] (LOGBACK-1418) Allow {} within variable name definitions
by QOS.CH (JIRA) 03 Sep '18

03 Sep '18

Ceki Gülcü created LOGBACK-1418: ----------------------------------- Summary: Allow {} within variable name definitions Key: LOGBACK-1418 URL: https://jira.qos.ch/browse/LOGBACK-1418 Project: logback Issue Type: Improvement Environment: Example: <property name="TIME" value="%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}"/> <property name="OPERATOR_PATTERN" value="${TIME} ${NODE} %X{user} %.8t %5le %40logger{40} %msg%n" /> Note {} after the %d in the value for TIME. Reporter: Ceki Gülcü Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1279) Async appenders do not scale well across multiple threads
by QOS.CH (JIRA) 31 Aug '18

31 Aug '18

1 0

[JIRA] (LOGBACK-1417) Better error reporting than IllegalArgumentException, All tokens consumes but was expecting "}"
by QOS.CH (JIRA) 29 Aug '18

29 Aug '18

Ceki Gülcü created LOGBACK-1417: ----------------------------------- Summary: Better error reporting than IllegalArgumentException, All tokens consumes but was expecting "}" Key: LOGBACK-1417 URL: https://jira.qos.ch/browse/LOGBACK-1417 Project: logback Issue Type: Improvement Components: logback-core Environment: To reproduce: case 1) define a pattern with no ending }. case 2) define a pattern in property and refer to it in a Layout, also pattern with no ending } Reporter: Ceki Gülcü Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1192) Stuck Thread Issue due to file system got full with logs
by QOS.CH (JIRA) 25 Aug '18

25 Aug '18

1 0