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

[JIRA] (LOGBACK-1344) RollingCalendar invalid "period barrier crossed" computation
by QOS.CH (JIRA) 09 Aug '22

09 Aug '22

1 0

[JIRA] (LOGBACK-1579) Hourly rolling policy not working
by QOS.CH (JIRA) 09 Aug '22

09 Aug '22

1 0

[JIRA] (LOGBACK-1579) Hourly rolling policy not working
by QOS.CH (JIRA) 09 Aug '22

09 Aug '22

1 0

[JIRA] (LOGBACK-1344) RollingCalendar invalid "period barrier crossed" computation
by QOS.CH (JIRA) 09 Aug '22

09 Aug '22

1 0

[JIRA] (LOGBACK-1652) better handling of malformed properties file
by QOS.CH (JIRA) 09 Aug '22

09 Aug '22

1 0

[JIRA] Updates for LOGBACK-1653: Logback stops logging while running
by QOS.CH (JIRA) 09 Aug '22

09 Aug '22

logback / LOGBACK-1653 [Open] Logback stops logging while running ============================== 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-1653 ============================== Issue created ------------------------------ halibobo1205 created this issue on 09/Aug/22 5:37 AM Summary: Logback stops logging while running Issue Type: Bug Affects Versions: 1.2.9 Assignee: Logback dev list Attachments: logback.xml Components: logback-classic Created: 09/Aug/22 5:37 AM Environment: Linux testgroup014 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) Priority: Major Reporter: halibobo1205 Description: During service running, the logs suddenly stop outputting and output normally after generating a new log file based on SizeAndTimeBasedRollingPolicy.Check the log related threads, no exceptions ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1652: better handling of malformed properties file
by QOS.CH (JIRA) 08 Aug '22

08 Aug '22

logback / LOGBACK-1652 [Open] better handling of malformed properties file ============================== 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-1652 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 08/Aug/22 11:29 PM Summary: better handling of malformed properties file Issue Type: Bug Assignee: Logback dev list Created: 08/Aug/22 11:29 PM Priority: Major Reporter: Ceki Gülcü Description: In case the properties file given to <variable> element is malformed, then an IllegalArgumentException may be thrown. {code:java} <configuration> <variable file="malformed.properties"/> </configuration> {code} {code:java} == Java Exception: java.lang.IllegalArgumentException: Malformed \uxxxx encoding. at java.base/java.util.Properties.loadConvert(Properties.java:672) at java.base/java.util.Properties.load0(Properties.java:456) at java.base/java.util.Properties.load(Properties.java:408) at ch.qos.logback.core.model.processor.PropertyModelHandler.loadAndSetProperties(PropertyModelHandler.java:87) at ch.qos.logback.core.model.processor.PropertyModelHandler.handle(PropertyModelHandler.java:50){code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1651: better error handling in case of missing <if> element in <if><then> pair
by QOS.CH (JIRA) 08 Aug '22

08 Aug '22

logback / LOGBACK-1651 [Open] better error handling in case of missing <if> element in <if><then> pair ============================== Here's what changed in this issue in the last few minutes. This issue has been created View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1651 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 08/Aug/22 10:58 PM Summary: better error handling in case of missing <if> element in <if><then> pair Issue Type: Bug Affects Versions: 1.3.0-alpha16 Assignee: Ceki Gülcü Created: 08/Aug/22 10:58 PM Fix Versions: 1.3.0-beta0 Priority: Major Reporter: Ceki Gülcü Description: The config file {code:xml} <configuration> <then/> </configuration>{code} results in {code:java} Java Exception: java.util.EmptyStackException at java.base/java.util.Stack.peek(Stack.java:101) at ch.qos.logback.core.model.processor.ModelInterpretationContext.peekModel(ModelInterpretationContext.java:73) at ch.qos.logback.core.model.processor.conditional.ThenModelHandler.handle(ThenModelHandler.java:45) {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1651) better error handling in case of missing <if> element in <if><then> pair
by QOS.CH (JIRA) 08 Aug '22

08 Aug '22

1 0

[JIRA] (LOGBACK-1650) Better error checking in case the config file tries to set the level of the ROOT logger to NULL
by QOS.CH (JIRA) 07 Aug '22

07 Aug '22

1 0