## Logback News

You can receive logback-related announcements by subscribing to the logback announce mailing list.

### xx of December 2008 - Release of version 0.9.14

Corrected a serious dead-lock problem occuring during configuration. It was reported in LBCLASSIC-81 by Holger Mense.

Corrected thread leakage observed with `TimeBasedRollingPolicy`'s `AsynchronousCompressor`. This bug was reported in LBCORE-78 by Szel Zoltan.

Added DuplicateMessageFilter, a turbo filter which detects duplicate messages, and beyond a certain number of repetitions, drops repeated messages.

`BasicStatusManager`'s internal buffer is now split into two parts, the header part and the tail part. The header part stores the fist H status messages whereas the tail part stores the last T messages. At present time H=T=150, although these values may change in future releases.

Fixed `NullPointerException` thrown when calling `setContextMap` on a fresh MDC. Issue was reported by Francois Terrier.

### 5th of December 2008 - Release of version 0.9.13

A `NullPointerException` was being thrown when a the level of a logger was set to null. The logger in question had to have children. This problem was reported in LBCLASSIC-91 by Mateusz Jedruch.

### 4th of December 2008 - Release of version 0.9.12

Fixed bug LBCORE-26 reported by Tsutomu YANO and independently by Hontvári József and Gamaliel Amaudruz. `RollingFileAppender` when used in conjunction with `DateBasedRollingPolicy` will rollover existing log files at initialization if their timestamp warrants it.

Added support for file appending in prudent mode. Thus, multiple `FileAppender` instances running on multiple JVMs can safely write to the same log file. With certain limitations, prudent mode extends to `RollingFileAppender`.

Fixed LBCLASSIC-83. It is now possible to set the level of a logger to null, even if it was previously set to a non-null level. Previously, a `NullPointerException` would be thrown.

In reponse to LBCLASSIC-61, LBCLASSIC-33, LBCLASSIC-24 and LBCLASSIC-14 `JMXConfigurator` has been redesigned.

Fixed LBGENERAL-22. The log4j.properties translator web-application has been significatnly refactored.

Fixed improvement request LBCLASSIC-59 relation to StatusListeners, originally submitted by Anton Tagunov.

The logger and class name converters now consider zero as having special meaning, and will return the simple class name, removing the package name prefix. This feature was asked by Silvano Maffeis.

In response to LBCLASSIC-54 support for turbo filters has refactored. The present code is safe under concurrent access while still offering good performance.

Fixed LBCORE-43 reported by Bruno Navert. Configuration files can now look up property files from classpath resources.

Fixed LBCLASSIC-86 related to `AccessControlException` thrown when run in a JVM with a `SecurityManager`.

Invoking the `LoggerContext.reset()` method resets logger levels to their default value, that is `DEBUG` for the root logger and `null` for all other loggers. This was requested in LBCLASSIC-90 by Mateusz Jedruch.

Fixed bug LBCLASSIC-69 reported by Anton Tagunov. The LevelToSyslogSeverity now correctly handles the TRACE level.

Fixed bug LBCLASSIC-57 reported by Anton Tagunov. SyslogAppender could overwhelm the Syslog server with very large messages. SyslogAppender now limits its message size to 256K.

Logback now supports setting the logger context name as well as inserting variables stored in JNDI as properties.

Fixed issue LBCLASSIC-49 reported by Oliver Lietz. The getLogger() method in `LoggerContext` class will now throw an `IllegalArgumentException` when invoked with a null argument.

### 28th of October 2008 - Release of version 0.9.11

Fixed LBCLASSIC-77 reported independenly by Gianni Doe, Yannick Haudry and Yossi Shaul. The childValue() method of `CopyOnInheritThreadLocal` class part of MDC code no longer throws a `NullPointerException`.

### 27th of October 2008 - Release of version 0.9.10

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 `reset`() 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.

### 26th of March 2008 - Release of version 0.9.9

MDC data in now inherited by child threads. This behaviour was already specified in the javadocs. The issue was raised by Martin Benda in bug 64 and independently by Peter Huber.

Logback no longer includes retro-weaver generted jars for JDK 1.4. There seemes to be little interest in JDK 1.4 builds. Calling retro-weaver increases logback's build time by a few seconds each time – seconds in which we can do more productive things.

Fixed bug 104, silly but but nonetheless serious copy-and-paste errors in the c.q.l.classic.Logger class, reported by Joern Huxhorn.

Having been replaced by `SimpleSocketServer`, the `SocketServer` class has been removed.

Fixed bug 105, sockets created by `SocketAppenderBase` is now closed, reported by Joern Huxhorn. More generally, `SimpleSocketServer` is much more careful to track open client connections and to close them.

Fixed bug 110 in relation with the `requestParameterMap` field in `AccessEvent` - reported by Joern Huxhorn.

Fixed SLF4J bug 66 in relation with caller data when using log4j-over-slf4j - reported by Frnack Routier.

Fixed bug 129 reported by Michael Franz. As a result, Joran now supports nested as well as multiple file inclusions.

Fixed bug 100 reported by Joern Huxhorn. At serialization time, object array passed as parameter, when the LoggingEvent is are now serialized as strings.

Fixed bug 109 reported by Joern Huxhorn. There should no longer be any NullPointerExceptions thrown by deserialized `AccessEvent` instances.

Fixed bug 8 reported by Sebastien Pennec. The documentation has been updated to reflect the fact that that in the context of conversion patterns the percent sign carries special meaning, in order to include the percent sign as a literal, it must be escaped with a backslash.

Fixed bug 52 reported by Kenichi Masuko. The bug has been fixed on March 8th, 2007. Starting with this release, Joran will support the injection of any enum tpye, not just `FilterReply`.

### 22th of August 2007 - Release of version 0.9.8

This version of logback synchronizes with SLF4J version 1.4.3. In particular, logback now natively supports SLF4J's MDC API introduced in SLF4J version 1.4.1. If you are using SLF4J version 1.4.1 or later please make sure upgrade to logback version 0.9.8 or later.

Fixed a number of documentation related bugs, in particular bug 90 reported by Luc Maisonobe and bug 88 reported by Sebastian Davids.

It is now possible to include configuration file fragments (in XML) as a resource. Previously, it was only possible to include a file by specifying a path to a file or a URL. This feature was requested by Michael Newcomb in bug 89.

Fixed caller data extraction problem as reported in bug 78 by Hans van der Meer.

The LoggingEvent class' constructor now correctly takes into account the argument array passed by the user. This problem was reported in bug 85 by Robert Christian.

### 29th of May 2007 - Release of version 0.9.7

This release corrects packaging bugs 75 and 76 related to the migration of logback to SLF4J version 1.4.0. There are no other changes.

### 23rd of May 2007 - Release of version 0.9.6

Logback is now aligned and compatible with SLF4J version 1.4.0, thus correcting bug 73 as reported by Andy Gerweck.

Fixed `NoClassDefFoundError` problem when running under JDK 1.4 as reported by Brian Suksomwong.

Fixed bug 63 as reported by La Canea Rosario. Calling log4j (bridge) with the trace level will no longer cause an IllegalStateException to be thrown.

Fixed bug 70 as reported by Dirk Ooms. The %throwable conversion word is now recognized as documented in the logback manual. Moreover, the manual now mentions the %nopex word which can be used to force `PatternLayout` to ignore the exception contained in the logging request.

As in most releases, the documentation has been improved.

### April 2nd, 2007 - Release of version 0.9.5

Fixed methods `isInfoEnabled`, `isWarnEnabled` and `isErrorEnabled` methods in `ch.qos.logback.classic.Logger` class which failed to work correctly. This bug was reported today by Pavel Kral on the slf4j-user list.

Contrary to previous versions of logback, the various Logger.isXYZEnabled(Marker) methods now take into account the marker information passed as parameter.

As discussed in bug 54, during automatic initialization, it makes better sense to first check for logback-test.xml file and only if that fails, to check for logback.xml. Maven2 will guarantee that the logback-test.xml file, if places undder test/resources will not be included in the artifact it produces.

### March 29th, 2007 - Release of version 0.9.4

Significant bug fixes made to `c.q.l.access.TeeFilter` and Co. Images and other binary files are now intercepted and replayed correctly. As for "x-www-form-urlencoded" post requests, their input buffer is left untouched. In a best-effort attempt, the input buffer for "x-www-form-urlencoded" post requests is later reconstructed through the request parameters. However, it may differ from the original buffer.

The logback team released today the first version of a plugin for Eclipse that allows developpers to visualize logs generated by a running application. It offers several nice features. Please check the console plugin-in guide for more details.

### March 20th, 2007 - Release of version 0.9.3

Includes in configuration files are now supported by Joran, logback's configuration framework. A file can contain an include element that has a file or url attribute pointing to a configuration file. See the chapter about configuration in the logback's online manual for more information.

Corrected bug 53 reported by Wilkins Poe. There is now a dependencies page that shows the requirements of each of logback's modules.

After a discussion on the SLF4J mailing list started by Franck Routier, a correction has been made when logging using the JCL104-over-slf4j module. Logback now correctly shows the caller location information.

As in most logback releases, the documentation has been improved.

### March 5th, 2007 - Release of version 0.9.2

The documentation is now in the docs/ directory to allow an easier access to the logback manual and website for offline viewing.

### March 5th, 2007 - Release of version 0.9.1

Logback-class now depends on SLF4J version 1.3.0 instead of 1.2.

Numerous improvements to the documentation.

Bug #46 reported by Mark Renyolds has been fixed. The `TimeUtilTest` should now run fine under any time zone.

Bug #45, also reported by Mark Reynolds, has been fixed. There should be no `ClassCastException` thrown anymore when passing an `Object` to the printing methods using the log4j-bridge module.

### January 31st, 2007 - Release of version 0.9

This version contains a new component, namely the `ContextSelector`, that provides context separation and management when logback is used by several web-apps running under the same server. A new chapter was added to the logback manual to detail the use of the `ContextSelector`, along with its associated components.

The `JMXConfigurator` has been improved. It now shows the context's Status objects, which lets users check the internal state of logback.

The logback manual's chapter 2, about logback's architecture, has been updated with two sections: Under the hood and Performance.

### January 23th, 2007 - Release of version 0.8.1

This version contains new components in the Access module, allowing users to display the full HttpServletRequest or HttpServletResponse of an access event.

The documentation section has been updated. The short introduction was split into the chapter 1 and chapter 2 of the logback manual. The chapters about Appenders and Layouts have been updated to document new components of logback.

A demonstration webApp presenting logback's major components is available. A document explains how to run it, and provides a step-by-step visit of the demo.

A first translation of logback jars to JDK1.4 is present in this release.

### January 12th, 2007 - Release of version 0.8

This version contains a whole new chapter, namely Chapter 3, about logback configuration. Several other documentation pages have been improved.

Logback now uses Generics in many components.

Several new components have been added to logback. A JMX Configurator now allows users to see and modify loggers or reload configuration among other possibilities. A document about this configurator is available in the corresponding section of the site. We'd like to thank Sebastian Davids for his ideas and contributions to this component.

A JMSTopicAppender and JMSQueueAppender are now available, as well as two new filters: LevelFilter and ThresholdFilter. A refactoring was done in the filters objects to ease the implementation of custom filters.

### December 19th, 2006 - Release of version 0.7.1

Version 0.7.1 of logback has been released.

This version contains more detailled information about logback access module, and its JMX components. A dedicated page explains how to configure and use logback access in Tomcat and Jetty, and access some of its components via JMX.

### December 18th, 2006 - Release of version 0.7

Version 0.7 of logback has been released.

Logback now ships with a new module: log4j-bridge. This new module can be used to intercept log4j calls and redirects them to logback components. More information about this module can be found in the corresponding documentation page.

The documentation has been vastly updated. Two new chapters, namely Filters and MDC, are available in the manual section.

### November 30th, 2006 - Release of version 0.6

Version 0.6 of logback has been released.

Logback classic now supports automatic configuration, allowing test and production environment configuration. `TurboFilters` make their first appearance in a logback release. They provide ultra-fast filtering possibilities. The logging context now supports listeners which will be contacted each time the context is reset or started. `SMTPAppender` allows for much more flexible configuration than before.

In logback access, new Appenders are available, namely `SocketAppender` and `DBAppender`. Logback access now supports filtering and event evaluations. A `CountingFilter` has been added. It provides statistical views of server access, reachable via JMX.

The documentation has also been improved. A complete new chapter has been added about Appenders, the short introduction to logback classic has been updated and a new module, containing many configuration examples has been added.

Logback now uses continous integration in its development.

Tests have been improved, many new have been added. This release also provides some bug fixes.

### October 26th, 2006 - Release of version 0.5

Version 0.5 of logback has been released.

This release offers a important improvements in Joran. In particular, Joran can now replay configuration elements.

As in the previous release, a major area of work is the documentation which is being continously improved.

### October 9th, 2006 - Release of version 0.4

Version 0.3 of logback has been released.

This release includes an improved access module, with specific implementations for the Jetty and Tomcat servers. Documentation was also added to show how to integrate logback-access with Jetty.

As for the classic module, several appenders and layouts have been added or improved. The error reporting of logback has also been enhanced, presenting the user with a link to an online page explaining possible reasons for the error.

A joran documentation was added, with examples in the core module.

### September 8th, 2006 - Release of version 0.3

Version 0.3 of logback has been released.

This release offers several new Appenders, support for Mapped Diagnostic Context, improved tests and documentation

In response to a bug report by Rickard Nilsson on the logback mailing list, a bug affecting parametrized logging was fixed.

We also released a PropertiesTranslator webapp that converts log4j.properties files to joran configuration files (in XML format).

### August 23th, 2006 - Release of version 0.2.5

Version 0.2.5 of logback has been released.

This release offers better documentation. With a number of correction mande in the short introduction to logback-classic.

### August 15th, 2006 - Release of version 0.2

Version 0.2 of logback has been released.

It offers better tests, a few more functionalities, and enhanced documentation. We also improved the site design to make it simpler and more efficient.

### July 26th, 2006 - Release of version 0.1

Version 0.1 of logback has been released.

### February 9th, 2006 - Logback web-site goes live

The logback web-site goes live on the 9th of February. At its present state, it is pretty primitive but updates will follow.