October 2013 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-760) Failed to instantiate LoggerContext
by Tony Trinh (JIRA) 20 Oct '13

20 Oct '13

1 0

[qos-ch/logback] 959291: Fixed issue "Failed to instantiate LoggerContext" ...
by Tony Trinh 20 Oct '13

20 Oct '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 959291a5b57cfdb2b6dbd0c7623a8d2313c163c5 https://github.com/qos-ch/logback/commit/959291a5b57cfdb2b6dbd0c7623a8d2313… Author: Norbert Kenderesi <norbert.kenderesi(a)bitknights.com> Date: 2013-10-18 (Fri, 18 Oct 2013) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/util/Loader.java Log Message: ----------- Fixed issue "Failed to instantiate LoggerContext" because of " java.lang.SecurityException: AccessController.checkPermission is unsupported." (LOGBACK-760) using the solution provided in the comment by ori. Commit: 772f7bf5838bda885c055cf011167b25cd58e36c https://github.com/qos-ch/logback/commit/772f7bf5838bda885c055cf011167b25cd… Author: Tony Trinh <tony19(a)gmail.com> Date: 2013-10-20 (Sun, 20 Oct 2013) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/util/Loader.java Log Message: ----------- Merge pull request #154 from wildhemp/master Fix for LOGBACK-760. Compare: https://github.com/qos-ch/logback/compare/071a93e9fbab...772f7bf5838b

1 0

[JIRA] (LOGBACK-350) SocketNode constructor blocks due to ObjectInputStream creation
by Richard Fearn (JIRA) 19 Oct '13

19 Oct '13

1 0

exceptionMessageIncluded parameter for SyslogAppender
by Roman Ivanov 18 Oct '13

18 Oct '13

Hi Developers, Does it make sense to extend SysLogAppender with "throwableMessageAppended" field to allow attach Exception/Throwable message to event ? Reason: Syslog is non linux/unix event logging system that does not support multi-line, so java developers play with substitution of EndOfLine symbols to make it conform unix rules for event logging. But in this case event become unreadable if full stacktrace is in event. It is most likely required only to see Exception message and then decide how to react on problem. No message nor full stacktrace is enough to investigate and fix problem - developer need see full log from job and context of event before. So having ability to have in Syslog only exception message is more convenient and short. In detail, and examples: http://roman-ivanov.blogspot.com/2013/10/logging-exception-message-in-log-e… Thanks, Roman Ivanov

2 2

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by Hrotkó Gábor (JIRA) 18 Oct '13

18 Oct '13

1 0

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by birupakshya (JIRA) 18 Oct '13

18 Oct '13

1 0

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by Hrotkó Gábor (JIRA) 18 Oct '13

18 Oct '13

1 0

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by birupakshya (JIRA) 18 Oct '13

18 Oct '13

1 0

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by Hrotkó Gábor (JIRA) 18 Oct '13

18 Oct '13

1 0

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by birupakshya (JIRA) 18 Oct '13

18 Oct '13

1 0