2.0.1

Release date

2014-07-29

This is the first patch release of Log4j 2.0 which contains numerous bug fixes.

Apache Log4j 2.0.1 requires a minimum of Java 6 to build and run. Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the very implementation specific classes and methods. The package names and Maven groupId have been changed to org.apache.logging.log4j to avoid any conflicts with Log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Log4j 2 website.

Added

  • Added documentation for Custom Levels and Custom Loggers. (LOG4J2-710)

  • Added WebLoggerContextUtils class to log4j-web for helper methods useful for asynchronous servlets. (LOG4J2-725)

Changed

  • Update to LMAX Disruptor 3.3.0 from 3.2.1. (LOG4J2-732)

  • Update to latest Jackson jars from the 2.4.1.X line. (LOG4J2-733)

Fixed

  • Fixed ClassLoader issues in loading Log4j providers in an OSGi environment. (LOG4J2-373)

  • Fixed AbstractDatabaseManager to close connection on writeInternal error. (LOG4J2-657)

  • DatePatternConverter ISO8601_PATTERN now conforms to ISO8601. (LOG4J2-670)

  • Android: Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup. (LOG4J2-703)

  • Improved error message if configuration file not found. (LOG4J2-704)

  • Android: java.lang.VerifyError: org/apache/logging/log4j/core/util/Closer (LOG4J2-713)

  • Automatically disable log4j JMX when detecting we are running on Android. (LOG4J2-716)

  • Correctly handle NetworkOnMainThreadException thrown on Android during Log4j2 initialization. (LOG4J2-719)

  • Updated documentation regarding extensions to LoggerContextFactory and Log4j 2 providers. (LOG4J2-731)

  • Fixed log4j-bom so that it won’t interfere with spring-bom and others. (LOG4J2-735)

  • Fixed log4j-bom so that it won’t specify a default scope on any third party dependencies. (LOG4J2-736)

  • RollingFileManager deadlock if async action thread fails to start. (LOG4J2-738)

  • Fixed typo in webapp manual regarding sample web.xml file. (LOG4J2-740)

  • Reinstate the package configuration attribute for discovering custom plugins. (LOG4J2-741)

  • XInclude not working with relative path. (LOG4J2-742)

  • Avoid unnecessary Clock calls when TimestampMessage is logged. (LOG4J2-744)

  • Retain the default date pattern after fixing the ISO8601 pattern. (LOG4J2-749)

  • Webapp configuration page has incorrect class name. (LOG4J2-750)