- logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCLASSIC-76) Allow extension of LoggingEvent with new data
by Ceki Gulcu (JIRA) 27 Oct '08

27 Oct '08

Allow extension of LoggingEvent with new data ---------------------------------------------- Key: LBCLASSIC-76 URL: http://jira.qos.ch/browse/LBCLASSIC-76 Project: logback-classic Issue Type: New Feature Affects Versions: 0.9.10 Reporter: Ceki Gulcu Assignee: Ceki Gulcu Fix For: 0.9.11 Let developers add extensions to LoggingEvent. For example, if a developer wanted to have their own implementation of MDC, say XMDC, they have no elegant way of adding it to LoggingEvent. -- 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 1

[JIRA] Resolved: (LBCORE-49) LogbackMDCAdapter allocates new HashMap for every MDC call
by Ceki Gulcu (JIRA) 27 Oct '08

27 Oct '08

[ http://jira.qos.ch/browse/LBCORE-49?page=com.atlassian.jira.plugin.system.i… ] Ceki Gulcu resolved LBCORE-49. ------------------------------ Fix Version/s: unspecified Resolution: Won't Fix Matt, I do not wish to change the code to support special use cases, especially because I think it would be easy to implement an alternative MDC implementation without the "copy on modify" behavior, say XMDC. Once you have written XMDC, you would also need an XMDCConverter. Assuming that you do not wish to serialize XMDC values in the LoggingEvent, those would be the only two required additions, i.e. approx. 1 hour of work. You could add XMDC values to LoggingEvent by modifying its argument array. For example, if you converted the XMDC key/value pairs into strings, adding them to the event's argument array would have them serialized in the event. Anyway, if you wish to pursue this venue, we could work on a more elegant way on extending the LoggingEvent object. Please create a new issue if extending LoggingEvent is a path you would wish to explore. > LogbackMDCAdapter allocates new HashMap for every MDC call > ---------------------------------------------------------- > > Key: LBCORE-49 > URL: http://jira.qos.ch/browse/LBCORE-49 > Project: logback-core > Issue Type: Bug > Components: Other > Affects Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Matt Finn > Assignee: Logback dev list > Fix For: unspecified > > Attachments: mdc-diff.txt > > > A new HashMap is allocated in logback's MDC implementation for every call to MDC.put and MDC.remove. > This can lead to excessive garbage collector load in performance critical code that makes very frequent use of MDC, such as asynchronous network and file IO code. > For certain programs it is critical to have MDC capability in code hotspots, where MDC is a valuable debugging tool as applied to TRACE and DEBUG statements. > The current implementation causes a load on the garbage collector even when logging is turned off. -- 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 0

[JIRA] Created: (LBCORE-54) FileAppender to support FileNamePattern option
by Chris Cheshire (JIRA) 27 Oct '08

27 Oct '08

FileAppender to support FileNamePattern option ---------------------------------------------- Key: LBCORE-54 URL: http://jira.qos.ch/browse/LBCORE-54 Project: logback-core Issue Type: Improvement Components: Appender Environment: Any Reporter: Chris Cheshire Assignee: Logback dev list It would be very useful if the base FileAppender supported the FileNamePattern option, the same as the rolling policy classes do for the RollingFileAppender. This will allow for log files to be created directly into a date based directory in the format of "logs/yyyy/MM/dd/appname.log". -- 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

2 6

[JIRA] Closed: (LBSITE-13) Logback manual refers to a not existing function in org.slf4j.MDC
by Ceki Gulcu (JIRA) 27 Oct '08

27 Oct '08

[ http://jira.qos.ch/browse/LBSITE-13?page=com.atlassian.jira.plugin.system.i… ] Ceki Gulcu closed LBSITE-13. ---------------------------- > Logback manual refers to a not existing function in org.slf4j.MDC > ----------------------------------------------------------------- > > Key: LBSITE-13 > URL: http://jira.qos.ch/browse/LBSITE-13 > Project: logback-site > Issue Type: Bug > Components: Documentation > Affects Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Michael Franz > Assignee: Logback dev list > Fix For: 0.9.10 > > > The logback manual chapter 7 says: > package org.slf4j; > public class MDC { > ... > //Returns the keys in the MDC as a Set. The returned value can be null. > public static Set<String> getKeys(); > } > But the method getKeys() is not part of the released slf4j API (versions 1.4.3 and 1.5.0). > This method exists only within the LogbackMDCAdapter. -- 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 0

svn commit: r1884 - in logback/trunk: . logback-access logback-classic logback-core logback-examples logback-site
by noreply.ceki＠qos.ch 27 Oct '08

27 Oct '08

Author: ceki Date: Mon Oct 27 21:58:07 2008 New Revision: 1884 Modified: logback/trunk/logback-access/pom.xml logback/trunk/logback-classic/pom.xml logback/trunk/logback-core/pom.xml logback/trunk/logback-examples/pom.xml logback/trunk/logback-site/pom.xml logback/trunk/pom.xml Log: 11 comes after 10 Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Mon Oct 27 21:58:07 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10</version> + <version>0.9.11-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Mon Oct 27 21:58:07 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10</version> + <version>0.9.11-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Mon Oct 27 21:58:07 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10</version> + <version>0.9.11-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Mon Oct 27 21:58:07 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10</version> + <version>0.9.11-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Mon Oct 27 21:58:07 2008 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10</version> + <version>0.9.11-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Mon Oct 27 21:58:07 2008 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10</version> + <version>0.9.11-SNAPSHOT</version> <packaging>pom</packaging> <name>Logback-Parent</name>

1 0

svn commit: r1883 - logback/tags/release_0.9.10/trunk
by noreply.ceki＠qos.ch 27 Oct '08

27 Oct '08

Author: ceki Date: Mon Oct 27 21:57:25 2008 New Revision: 1883 Added: logback/tags/release_0.9.10/trunk/ - copied from r1882, /logback/trunk/ Log: tagging 0.9.10

1 0

svn commit: r1882 - logback/tags/release_0.9.10
by noreply.ceki＠qos.ch 27 Oct '08

27 Oct '08

Author: ceki Date: Mon Oct 27 21:56:58 2008 New Revision: 1882 Added: logback/tags/release_0.9.10/ Log: tagging 0.9.10

1 0

Release of logback version 0.9.10
by Ceki Gulcu 27 Oct '08

27 Oct '08

27th of October 2008 - Release of version 0.9.10 After a lull of 7 months, I am happy to announce the release of logback version 0.9.10. This version includes both bug fixes as well as significant enhancements. Here is the list: In case of errors during initialization, logback-classic now automatically prints out its internal status. This has been a frequently requested feature. The LogbackValve in logback-access (ensuring integration with Tomcat), will now systematically print its internal status upon initialization, unless told to be quiet. This greatly helps troubleshooting the configration of logback-access under Tomcat. Fixed bug 147 which occured when the user inadvertently attempted to set the layout of a SyslogAppender. The code now actively prevents this. Documenation has been updated to reflect the change. Fixed bug LBCLASSIC-56 originally reported by Michel Colette. Backslash characters are now correctly interpreted in filename patterns. The TurboFilterChain in a LoggerContext is now cleared when the shutdownAndReset method is called. This problem was reported on May 1st, 2008, by Julia Hu on the logback developpers list. Fixed issue LBCORE-48. During rollover, compression of large files would bring all logging to a halt. In this latest release, the rolled over file is first renamed, which is a relatively fast operation, and only then is the renamed file compressed asyncronously (in a separate thread). Fixed issue LBCORE-11. It is now possible to instruct TimeBasedRollingPolicy to delete old files, thus controlling then number of archived log files. Fixed issue LBCORE-42. If the parent directory of the log file does not exist, then FileAppender will create it, including any necessary but nonexistent parent directories. Fixed LBCORE-15 reported by Klaus Unger and others. DBAppender should now work with Oracle 9, 10g and 11g, regardless of the JDBC driver type used. Fixed issue LBCORE-17 reported by Thorbjørn Ravn Andersen. Logback now relies on Geronimo JMS API specifications instead of Sun's JMS API specification, the latter requiring manual installation. With Geronimo JMS, logback can be built using Maven without needing to manually install any dependencies. Fixed issue LBCORE-23. In PatternLayout, parenthesis can be used to group conversion patterns. It follows that the '(' and ')' carry special meaning and need to be escaped to be used as literals. This is now properly documented. The location of the default configuration file can be specified by a system property. This feature was requested in LBCORE-32 by Ted Graham, Matt Fowles, Ivan Biddles and Ralph Goers. Fixed issue LBCORE-55 reported by Natan Cox. WriterAppender now outputs its presentation footer and file footer in the the correct order. Fixed issue LBCORE-27 reported by Peter Royal. SMTPAppender now outputs its presentation footer and file footer in the the correct order. Fixed issue LBCLASSIC-67 reported by Alessandro Fustini. SMTPAppender now correctly configures the layout used to format the subject line of the outgoing email. It no longer appends a lengthy stack trace to the subject line. Fixed issue LBCLASSIC-68 reported by Gili Tzabari. In environments where the TCCL (Thread Context Class Laoder) was not set, logback was unable to located its default configuraiton files. Logback now uses the class loader that loaded logback itself to locate its resources instead of the TCCL. This approach is simpler and deemed to cover more environments, i.e. more widely applicable. Fixed issue LBGENERAL-24 reported by Hung Tang. SMTPAppender now supports plain username/password authentication as well as both the STARTTLS command and SSL connections. Fixed issue LBCLASSIC-48 reported by Peter Royal. SyslogAppender now correctly outputs hours as 0-23 and not as 1-12 as previously. Added a new TurboFilter called DynamicThresholdFilter which can filter events depending on MDC values based on a variery of criteria such as company name, product or the end user. This filter was contributed by Ralph Goers in LBCLASSIC-53. You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://qos.ch/mailman/listinfo/logback-announce Enjoy, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

svn commit: r1881 - in logback/trunk: . logback-access logback-classic logback-core logback-examples logback-site
by noreply.ceki＠qos.ch 27 Oct '08

27 Oct '08

Author: ceki Date: Mon Oct 27 20:46:01 2008 New Revision: 1881 Modified: logback/trunk/logback-access/pom.xml logback/trunk/logback-classic/pom.xml logback/trunk/logback-core/pom.xml logback/trunk/logback-examples/pom.xml logback/trunk/logback-site/pom.xml logback/trunk/pom.xml Log: preparing release 0.9.10 Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Mon Oct 27 20:46:01 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10-SNAPSHOT</version> + <version>0.9.10</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Mon Oct 27 20:46:01 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10-SNAPSHOT</version> + <version>0.9.10</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Mon Oct 27 20:46:01 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10-SNAPSHOT</version> + <version>0.9.10</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Mon Oct 27 20:46:01 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10-SNAPSHOT</version> + <version>0.9.10</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Mon Oct 27 20:46:01 2008 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10-SNAPSHOT</version> + <version>0.9.10</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Mon Oct 27 20:46:01 2008 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.10-SNAPSHOT</version> + <version>0.9.10</version> <packaging>pom</packaging> <name>Logback-Parent</name>

1 0

svn commit: r1880 - in logback/trunk/logback-site/src/site/pages: . manual
by noreply.ceki＠qos.ch 27 Oct '08

27 Oct '08

Author: ceki Date: Mon Oct 27 20:34:59 2008 New Revision: 1880 Modified: logback/trunk/logback-site/src/site/pages/manual/filters.html logback/trunk/logback-site/src/site/pages/manual/joran.html logback/trunk/logback-site/src/site/pages/news.html Log: - rewording in filters.html - Added blurb on LBCORE-32 - various updates to news.html Modified: logback/trunk/logback-site/src/site/pages/manual/filters.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/filters.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/filters.html Mon Oct 27 20:34:59 2008 @@ -105,10 +105,11 @@ filter. - - The next class is all it takes to implement one's own filter. All it does is accept - logging events who's message contains the String sample. The filter will give a - neutral response to any logging event who's message does not contain this String. + The next class is all it takes to implement one's own + filter. All it does is accept logging events who's message + contains the String sample. The filter will give a + neutral response to any logging event who's message does not + contain this String. Example 6.1: Basic custom filter (<a href="../xref/chapter6/SampleFilter.html">logback-examples/src/main/java/chapter6/SampleFilter.java</a>) @@ -156,17 +157,17 @@ </root> </configuration></pre></div> - - Thanks to Joran, logback's powerful configuration framework, adding - an option to such a filter is very easy. Just add the corresponding - getter and setter methods in the class, and you can specify the - option's value in an xml element, nested within the filter element. + Thanks to Joran, logback's powerful configuration framework, + adding an option to such a filter is very easy. Just add the + corresponding getter and setter methods in the class, and you can + specify the option's value in an xml element, nested within the + filter element. - - In case you want to implement a filter that provides different behaviour - depending on the result of its test (say, a filter that would accept or deny - an event depending on the content of its message), you can extend the + In case you want to implement a filter that provides different + behaviour depending on the result of its test (say, a filter that + would accept or deny an event depending on the content of its + message), you can extend the <a href="../xref/ch/qos/logback/core/filter/AbstractMatcherFilter.html"> <code>AbstractMatcherFilter</code></a> class. It will provide your filter with two attribute: OnMatch and OnMismatch, that can be configured @@ -433,32 +434,32 @@ <a name="TurboFilter"></a> <h3>TurboFilters</h3> - - <code>TurboFilter</code> objects all extend the + <code>TurboFilter</code> objects all extend the <a href="../xref/ch/qos/logback/classic/turbo/TurboFilter.html"> - <code>TurboFilter</code></a> abstract class. Like the usual filters, they - use ternary logic to return their evaluation of the logging event. + <code>TurboFilter</code></a> abstract class. Like the regular + filters, they use ternary logic to return their evaluation of + the logging event. - - Overall, they work much like the previously mentionned filters. However, - there are two main differences between <code>Filter</code> and - <code>TurboFilter</code> objects. + Overall, they work much like the previously mentionned + filters. However, there are two main differences between + <code>Filter</code> and <code>TurboFilter</code> objects. - - <code>TurboFilter</code> objects are tied to the logging context. Hence, they - are called not only when a given appender is used, but each and every time a logging - request is issued. Their scope is wider than appender-attached filters. + <code>TurboFilter</code> objects are tied to the logging + context. Hence, they are called not only when a given appender is + used, but each and every time a logging request is issued. Their + scope is wider than appender-attached filters. More importantly, they are called before the - <code>LoggingEvent</code> object creation. Their decision is made - based on some of the logging event's components. They require no - logging event instantiation, nor any other treatement to provide - their filtering functionnalities. They are much more performant - than the usual <code>Filter</code> objects. - + <code>LoggingEvent</code> object creation. + <code>TurboFilter</code> objects do not require the instantiation + of a logging event to filter a logging request. As such, turbo + filters are intended for high performance filtering of logging + event, even before they are created. + + <h3>Implementing your own TurboFilter</h3> @@ -519,21 +520,20 @@ } </pre></div> - - The <code>TurboFilter</code> above accepts events that contain a specific marker. - If said marker is not found, then the filter passes the responsability to - the next filter in the chain. + The <code>TurboFilter</code> above accepts events that contain + a specific marker. If said marker is not found, then the filter + passes the responsability to the next filter in the chain. - - To allow more flexibility, the marker that will be tested can be specified - in the configuration file. Hence the getter and setter methods. We also implemented - the <code>start()</code> method, to check that the option has been specified during the - configuration process. + To allow more flexibility, the marker that will be tested can + be specified in the configuration file. Hence the getter and + setter methods. We also implemented the <code>start()</code> + method, to check that the option has been specified during the + configuration process. - - Here is a sample configuration that makes use of the newly created <code>TurboFilter</code>. + Here is a sample configuration that makes use of our newly + created <code>TurboFilter</code>. Example 6.7: Basic custom <code>TurboFilter</code> configuration (logback-examples/src/main/java/chapter6/sampleTurboFilterConfig.xml) @@ -556,18 +556,20 @@ </root> </configuration></pre></div> - - Logback classic ships with several <code>TurboFilter</code> classes ready for use. - The - <a href="../xref/ch/qos/logback/classic/turbo/MDCFilter.html"><code>MDCFilter</code></a> - check the presence of a given value in the MDC. On the other hand, - <a href="../xref/ch/qos/logback/classic/turbo/MarkerFilter.html"><code>MarkerFilter</code></a> - checks for the presence of a specific marker associated with the logging request. + Logback classic ships with several <code>TurboFilter</code> + classes ready for use. The <a + href="../xref/ch/qos/logback/classic/turbo/MDCFilter.html"><code>MDCFilter</code></a> + check the presence of a given value in the MDC whereas <a + href="../apidocs/ch/qos/logback/classic/turbo/DynamicThresholdFilter.html"><code>DynamicThresholdFilter</code></a> + allows filtering based on MDC key/level thresold associations. On + the other hand, <a + href="../xref/ch/qos/logback/classic/turbo/MarkerFilter.html"><code>MarkerFilter</code></a> + checks for the presence of a specific marker associated with the + logging request. - - Here is a sample configuration, using both <code>MDCFilter</code> and - <code>MarkerFilter</code>. + Here is a sample configuration, using both + <code>MDCFilter</code> and <code>MarkerFilter</code>. Example 6.8: <code>MDCFilter</code> and <code>MarkerFilter</code> Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/joran.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/joran.html Mon Oct 27 20:34:59 2008 @@ -328,6 +328,18 @@ printed. + <h3>Specifying the location of the default configuration file as a + system property</h3> + + If you wish, you can specify the location of the default + configuration file with a system property named + <code>logback.configurationFile</code>. The value of the this + property can be a URL, a resource on the class path or a path to a + file external to the application. + + + java -Dlogback.configurationFile=/path/to/config.xml chapter3.MyApp1 + <h3>Invoking <code>JoranConfigurator</code> directly</h3> Logback relies on a configuration library called Joran which is Modified: logback/trunk/logback-site/src/site/pages/news.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/news.html (original) +++ logback/trunk/logback-site/src/site/pages/news.html Mon Oct 27 20:34:59 2008 @@ -29,7 +29,7 @@ <hr width="80%" align="center" /> - <h3>XXth of October 2008 - Release of version 0.9.10</h3> + <h3>27th of October 2008 - Release of version 0.9.10</h3> In case of errors during initialization, logback-classic now automatically prints out its internal status. This has been @@ -82,6 +82,11 @@ directories. + Fixed <a href="http://jira.qos.ch/browse/LBCORE-15">LBCORE-15</a> + reported by Klaus Unger and others. DBAppender should now work with + Oracle 9, 10g and 11g, regardless of the JDBC driver type used. + + Fixed issue <a href="http://jira.qos.ch/browse/LBCORE-17">LBCORE-17</a> reported by Thorbjørn Ravn Andersen. Logback now relies on Geronimo JMS @@ -99,7 +104,10 @@ documented. - <a href="http://jira.qos.ch/browse/LBCORE-32">LBCORE-32</a> + The location of the default configuration file can be specified + by a system property. This feature was requested in <a + href="http://jira.qos.ch/browse/LBCORE-32">LBCORE-32</a> by Ted + Graham, Matt Fowles, Ivan Biddles and Ralph Goers. Fixed issue <a @@ -151,11 +159,13 @@ as 0-23 and not as 1-12 as previously. - <a href="http://jira.qos.ch/browse/LBCLASSIC-53">LBCLASSIC-53</a> + Added a new TurboFilter called DynamicThresholdFilter which can + filter events depending on MDC values based on a variery of criteria + such as company name, product or the end user. This filter was + contributed by Ralph Goers in <a + href="http://jira.qos.ch/browse/LBCLASSIC-53">LBCLASSIC-53</a>. - - <hr width="80%" align="center" />

1 0