- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 11 Mar '17

11 Mar '17

1 0

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

1 0

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

1 0

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

Carsten Röttgers created LOGBACK-1277: ----------------------------------------- Summary: Capping log files does not work with large log file base Key: LOGBACK-1277 URL: https://jira.qos.ch/browse/LOGBACK-1277 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.1.10 Reporter: Carsten Röttgers Assignee: Logback dev list I am using SizeAndTimeBasedRollingPolicy and I was wondering why logback ignores my totalSizeCap settings. totalSizeCap was set to 5GB and the total size of my log files was about 8GB. I started my application (a Spring Boot Application) and no files were removed. When testing with smaller settings (256MB totalSizeCap) files were removed as expected. So I debugged TimeBasedArchiveRemover.capTotalSize and found out that totalSize got negative. Making totalSize (and totalRemoved) long instead of int should fix the problem. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1276) %msg dissapear ( empty message log )
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

1 0

[JIRA] (LOGBACK-1276) %msg dissapear ( empty message log )
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

1 0

[JIRA] (LOGBACK-1276) %msg dissapear ( empty message log )
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

Dani Vainstein created LOGBACK-1276: --------------------------------------- Summary: %msg dissapear ( empty message log ) Key: LOGBACK-1276 URL: https://jira.qos.ch/browse/LOGBACK-1276 Project: logback Issue Type: Bug Components: logback-classic Environment: Windows7 Reporter: Dani Vainstein Assignee: Logback dev list *String* s = "ALL|RANDOM|NONE"; log.error( "My Message is :", s ); log.info( "My Message is : ", s ); log: 00:53:05.576 start-up-context | ERROR | <main> | "XlsRunnerParser.java" [ XlsRunnerParser.parse:118 ] - My Message is : 00:53:08.077 start-up-context | INFO | <main> | "XlsRunnerParser.java" [ XlsRunnerParser.parse:119 ] - My Message is : {color:#ff0000}The message is not printed!!{color} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1275) Make use of StackWalker API
by QOS.CH (JIRA) 09 Mar '17

09 Mar '17

1 0

[JIRA] (LOGBACK-1275) Make use of StackWalker API
by QOS.CH (JIRA) 09 Mar '17

09 Mar '17

Ceki Gülcü created LOGBACK-1275: ----------------------------------- Summary: Make use of StackWalker API Key: LOGBACK-1275 URL: https://jira.qos.ch/browse/LOGBACK-1275 Project: logback Issue Type: Improvement Components: logback-classic Environment: Make use of StackWalker API introduced in Java 9 Reporter: Ceki Gülcü Assignee: Logback dev list Fix For: 1.2.2 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1274) Logback swallows output from Exceptions overriding toString()
by QOS.CH (JIRA) 08 Mar '17

08 Mar '17

Claus created LOGBACK-1274: ------------------------------ Summary: Logback swallows output from Exceptions overriding toString() Key: LOGBACK-1274 URL: https://jira.qos.ch/browse/LOGBACK-1274 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.1 Environment: Windows, Java 8 Reporter: Claus Assignee: Logback dev list Attachments: logback.xml, LoggerTest.java When logging exceptions that overwrite toString() then logback ignores the output of it. For example: {code:java} class OverridingException extends Exception { @Override public String toString() { return super.toString() + " important additional information"; } }{code} When used with logback the following code {code:java} @Test public void testName() { org.slf4j.Logger logger = LoggerFactory.getLogger(LoggerTest.class); try { throw new OverridingException(); } catch (Throwable t) { logger.error("", t); } }{code} produces output without the string "important additional information" {code:java} 2017-03-08 16:44:27 [main] ERROR trial.LoggerTest - trial.LoggerTest$OverridingException: null at trial.LoggerTest.testName(LoggerTest.java:32){code} while Java Util Logging outputs correctly {code:java} Mär 08, 2017 4:44:27 PM trial.LoggerTest testLogging SCHWERWIEGEND: trial.LoggerTest$OverridingException important additional information at trial.LoggerTest.testLogging(LoggerTest.java:22){code} Testfile and logback.xml attached. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0