- logback-dev - mailman3.qos.ch

[qos-ch/logback] 892376: update date of release
by Ceki Gulcu 04 Dec '12

04 Dec '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 89237688457055ca4d89c901af551633e80bd0d4 https://github.com/qos-ch/logback/commit/89237688457055ca4d89c901af551633e8… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-12-04 (Tue, 04 Dec 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/selector/ContextJNDISelector.java M logback-classic/src/main/java/ch/qos/logback/classic/selector/DefaultContextSelector.java M logback-site/src/site/pages/css/screen.css M logback-site/src/site/pages/job.html M logback-site/src/site/pages/news.html M logback-site/src/site/pages/templates/left.js Log Message: ----------- update date of release

1 0

[JIRA] Created: (LBCLASSIC-260) Recording appender that dumps debug messages only when error occurs
by Tomasz Nurkiewicz (JIRA) 04 Dec '12

04 Dec '12

Recording appender that dumps debug messages only when error occurs ------------------------------------------------------------------- Key: LBCLASSIC-260 URL: http://jira.qos.ch/browse/LBCLASSIC-260 Project: logback-classic Issue Type: New Feature Components: appender Affects Versions: 0.9.28 Reporter: Tomasz Nurkiewicz Assignee: Logback dev list Provide built-in utility appender that silently stores last few logging messages and dumps them (forwards to a target appender) only when an error occurs. Older logging events are replaced with new ones. This is a configuration example: <configuration> <appender name="REC" class="ch.qos.logback.classic.RecordingAppender"> <appender-ref ref="STDOUT"/> <maxEvents>1000</maxEvents> <dumpThreshold>WARN</dumpThreshold> <expiryTimeMs>15000</expiryTimeMs> </appender> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%-4relative [%thread] %-5level - %msg%n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="REC"/> </root> </configuration> Such an appender is crafted manually by several users, it would be nice to provide it out of the box. I already implemented this feature (100% test coverage): https://github.com/nurkiewicz/logback/tree/recording-appender -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 3

[JIRA] (LOGBACK-771) Unable to configure yearly rollover
by Fried Hoeben (JIRA) 03 Dec '12

03 Dec '12

1 0

[JIRA] Created: (LBCLASSIC-301) MDC Adapter with configurable InheritableThreadLocal
by Alexander Treptow (JIRA) 01 Dec '12

01 Dec '12

MDC Adapter with configurable InheritableThreadLocal ---------------------------------------------------- Key: LBCLASSIC-301 URL: http://jira.qos.ch/browse/LBCLASSIC-301 Project: logback-classic Issue Type: Improvement Components: appender Affects Versions: 0.9.28 Reporter: Alexander Treptow Assignee: Logback dev list Priority: Minor Attachments: LogbackMDCAdapter.java In our application we use a sifting file appender to log bot requests to a different log file than normal user requests. We have several sensor and aggregation threads that are started on different times that also have some logging output. My Problem: Log statements from request-independent threads are posted to bot.log and main.log on random. My Solution: I patched the LogbackMDCAdapter to be configureable by a system variable, to disable inheritance of the thread local member "copyOnInheritThreadLocal". The patched version defaults to old behavior, so it doesn't change if you do not configure it. To disable inheritance of that member, just pass "logback.threadlocal.inherit.copy=false" to the JVM. I applied the patch to Version 0.9.28 and tested it with our application. Maybe other logback users also want to configure logback in that way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 4

[JIRA] (LOGBACK-770) Colon within syslog SuffixPattern converted to string messing up date
by Robert Blazewicz (JIRA) 30 Nov '12

30 Nov '12

1 0

[JIRA] Created: (LBCLASSIC-225) Please add system property to enable debugging of config loading
by Aaron Digulla (JIRA) 28 Nov '12

28 Nov '12

Please add system property to enable debugging of config loading ---------------------------------------------------------------- Key: LBCLASSIC-225 URL: http://jira.qos.ch/browse/LBCLASSIC-225 Project: logback-classic Issue Type: New Feature Components: joran Affects Versions: 0.9.26 Reporter: Aaron Digulla Assignee: Logback dev list This has bugged me several times already: There is no way to set ConfigurationAction.debugMode from a system property. Use cases: - Enable debugging for a quick check without modifying sources (= no accidental commit) - Enable debugging to figure out which logback config is loaded in production (for example if one crept into a JAR file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 11

[JIRA] Created: (LBGENERAL-50) Swing Logger GUI (edit level and show root logger)
by Laurent Bourges (JIRA) 27 Nov '12

27 Nov '12

Swing Logger GUI (edit level and show root logger) -------------------------------------------------- Key: LBGENERAL-50 URL: http://jira.qos.ch/browse/LBGENERAL-50 Project: logback-general Issue Type: New Feature Environment: linux x86_64 / sun jdk 1.6+ Reporter: Laurent Bourges Assignee: Logback dev list Priority: Trivial I was using JUL and loggui (http://www.informatrix.ch/loggui/index.html) to edit logger's level at runtime and look at application logs in our Swing applications; it is very useful when applications are deployed using Java Web Start (jnlp environment) I switched to SLF4J 1.6.4 / LOGBACK 1.0 last week. As I wanted LogGui features for LogBack, I made it = LogbackGui (1 single and standalone java class): This class provides two major functionnalities: - application log viewer - one simple log GUI : Logger hierarchy browser / Level editor and displays current logs This class is dedicated to Slf4j @see http://www.slf4j.org/ (MIT License) using Logback @see http://logback.qos.ch/ (EPL v1.0 / LGPL 2.1). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 4

[JIRA] (LOGBACK-769) incorrect variable substitution with nested default value
by Matthew Neeley (JIRA) 27 Nov '12

27 Nov '12

1 0

How to change the underlying buffer size of BufferedOutputStream used by logback's FileAppender?
by Tim Shi 23 Nov '12

23 Nov '12

We are using logback as our logging framework. We noticed that the FileAppender uses ResilientFileOutputStream which is backed by an BufferedOutputStream. We are wondering if there's a way to configure the buffer size of this BufferedOutputStream instance so that we can tune the performance of logback. Thanks, Tim

1 0

[JIRA] Created: (LBCORE-239) Minimal XSD schema for the Logback XML configuration file
by Geoffrey De Smet (JIRA) 14 Nov '12

14 Nov '12

Minimal XSD schema for the Logback XML configuration file --------------------------------------------------------- Key: LBCORE-239 URL: http://jira.qos.ch/browse/LBCORE-239 Project: logback-core Issue Type: New Feature Components: Other Affects Versions: 1.0.0 Reporter: Geoffrey De Smet Assignee: Logback dev list Although it's probably impossible to have an XSD schema that has every possible configuration element, it's possible to provide a valid XSD that allows any element at certain places, but does have a list of the common (= minimal set) of configuration elements, such as <configuration>, <appender> and <root>. How to have a specific element that can have any child element? {code}  <xs:element name="appender" minOccurs="0"> <xs:annotation> <xs:documentation source="version">1.0.0</xs:documentation> <xs:documentation source="description">TODO The appender ...</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:any minOccurs="0" maxOccurs="unbounded" processContents="skip"/> </xs:sequence> </xs:complexType> </xs:element> {code} Benefits: - Can be used to validate the xml in IntelliJ/Eclipse, without having to run it. - Code completion for XML in IntelliJ/Eclipse - The XSD description can explain what those "minimal" elements do. With IntelliJ (and Eclipse?) that "javadoc" pops up when writing it. - Can also be used by logback itself to validate the xml at runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 2