Entries tagged [log4j2]

Monday December 16, 2019

LOG4J2 2.13.0 Released

The Apache Log4j 2 team is pleased to announce the Log4j 2.13.0 release!

Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as support for Markers, lambda expressions for lazy logging, property substitution using Lookups, multiple patterns on a PatternLayout and asynchronous Loggers. Another notable Log4j 2 feature is the ability to be "garbage-free" (avoid allocating temporary objects) while logging. In addition, Log4j 2 will not lose events while reconfiguring.

The artifacts may be downloaded from https://logging.apache.org/log4j/2.x/download.html.

This release contains bugfixes and minor enhancements. Some of the new features in this release are:

  1. Log4j 2 now requires Java 8 or higher to build and run.
  2. Experimental support for Log4j 1 configuration files. See Log4j 2 Compatiblity with Log4j 1.
  3. The Logger API has been enhanced to support a builder pattern. This can dramatically improve the overhead of capturing location information. See Log Builder.
  4. Better integration with Spring Boot by providing access to Spring variables in Log4j 2 configuration files and allowing Log4j 2 system properties to be defined in the Spring configuration. See Logging in the Cloud.
  5. Support for accessing Kubernetes information via a Log4j 2 Lookup.
  6. The Gelf Layout now allows the message to be formatted using a PatternLayout pattern. Logging in the Cloud provides an example of this, as well as the use of the Spring and Kubernetes Lookups.

Due to a break in compatibility in the SLF4J binding, Log4j now ships with two versions of the SLF4J to Log4j adapters. log4j-slf4j-impl should be used with SLF4J 1.7.x and earlier and log4j-slf4j18-impl should be used with SLF4J 1.8.x and later.

Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they no longer have the "timeMillis" attribute and instead have an "Instant" element with "epochSecond" and "nanoOfSecond" attributes.

The Log4j 2.13.0 API, as well as many core components, maintains binary compatibility with previous releases.

GA Release 2.13.0

Changes in this version include:

New Features

  • LOG4J2-2732: Add ThreadContext.putIfNotNull method. Thanks to Matt Pavlovich.
  • LOG4J2-2731: Add a Level Patttern Selector.
  • LOG4J2-63: Add experimental support for Log4j 1 configuration files.
  • LOG4J2-2716: Add the ability to lookup Kubernetes attributes in the Log4j configuration. Allow Log4j properties to be retrieved from the Spring environment if it is available.
  • LOG4J2-2710: Allow Spring Boot application properties to be accessed in the Log4j 2 configuration. Add lower and upper case Lookups.
  • LOG4J2-2639: Add builder pattern to Logger interface.

Fixed Bugs

  • LOG4J2-2058: Prevent recursive calls to java.util.LogManager.getLogger().
  • LOG4J2-2725: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler to clear memory correctly in case of exception/error Thanks to Dzmitry Anikechanka.
  • LOG4J2-2635: Wrong java version check in ThreadNameCachingStrategy. Thanks to Filipp Gunbin.
  • LOG4J2-2674: Use a less confusing name for the CompositeConfiguration source. Thanks to Anton Korenkov.
  • LOG4J2-2727: Add setKey method to Kafka Appender Builder. Thanks to Clément Mathieu.
  • LOG4J2-2707: ArrayIndexOutOfBoundsException could occur with MAC address longer than 6 bytes. Thanks to Christian Frank.
  • LOG4J2-2712: The rolling file appenders would fail to compress the file after rollover if the file name matched the file pattern.
  • LOG4J2-2693: @PluginValue does not support attribute names besides "value".
  • LOG4J2-2647: Validation blocks definition of script in properties configuration.
  • LOG4J2-2680: Set result of rename action to true if file was copied. Thanks to Guillermo Xavier Hurtado Garcia.
  • LOG4J-2672: Add automatic module names where missing. Thanks to Stephen Colebourne.
  • LOG4J2-2673: OutputStreamAppender.Builder ignores setFilter(). Thanks to Yuichi Sugimura.
  • LOG4J2-2725: Prevent a memory leak when async loggers throw errors. Thanks to Dzmitry Anikechanka.

Changes

  • LOG4J2-2701: Update Jackson to 2.9.10.
  • LOG4J2-2709: Allow message portion of GELF layout to be formatted using a PatternLayout. Allow ThreadContext attributes to be explicitly included or excluded in the GelfLayout.

Apache Log4j 2.13.0 requires a minimum of Java 8 to build and run. Log4j 2.3 was the last release that supported Java 6 and Log4j 2.11.2 is the last release to support Java 7.

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

https://logging.apache.org/log4j/2.x/

Monday June 25, 2018

[ANNOUNCE] Apache Log4j Audit 1.0.0 released

The Apache Log4j team is pleased to announce the Apache Log4j Audit 1.0.0 release!

Apache Log4j Audit provides a framework for defining audit events and then logging them using Log4j. The framework focuses on defining the events and providing an easy mechanism for applications to log them, allowing products to provide consistency and validity to the events that are logged. It does not focus on how the log events are written to a data store. Log4j itself provides many options for that. Log4j Audit builds upon Log4j by defining its own AuditMessage. An AuditMessage is a container for structured data messages which allows a log message to be generated that contains a set of keys and values. The AuditMessage passes through Log4j as any other log event would.

[Read More]

Saturday March 17, 2018

Log4j 2.11 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.11 release!

Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as support for Markers, lambda expressions for lazy logging, property substitution using Lookups, multiple patterns on a PatternLayout and asynchronous Loggers. Another notable Log4j 2 feature is the ability to be "garbage-free" (avoid allocating temporary objects) while logging. In addition, Log4j 2 will not lose events while reconfiguring.

This release contains new features, bugfixes and minor enhancements. One 2.11 feature worth highlighting is that log timestamps can now have microsecond or nanosecond precision when running on Java 9.

Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they no longer have the "timeMillis" attribute and instead have an "Instant" element with "epochSecond" and "nanoOfSecond" attributes.

[Read More]

Thursday November 23, 2017

Log4j 2.10 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.10 release!

Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as support for Markers, lambda expressions for lazy logging, property substitution using Lookups, multiple patterns on a PatternLayout and asynchronous Loggers. Another notable Log4j 2 feature is the ability to be "garbage-free" (avoid allocating temporary objects) while logging. In addition, Log4j 2 will not lose events while reconfiguring.

This release contains new features, bugfixes and minor enhancements. Some of the new features include support for the Java 9 module system, support for the new SLF4j 1.8 binding mechanism, simplification of the Log4j property naming scheme, and native support of Jetty's logger. Log4j API is now a fully compliant Java 9 module while the other Log4j jars are Java 9 named automatic modules.

This release supports both SLF4J 1.7.x and SLF4J 1.8.x. Because SLF4J 1.7.x requires implementations to include classes in the org.slf4j.impl package log4j-sl4j-impl cannot be used as a Java 9 module. Support for SLF4J 1.7.x will be removed in a future release.

As of Log4j 2.9.0, the Log4j API was modified to use java.util.ServiceLoader to locate Log4j implementations, although the former binding mechanism is still supported. The Log4j API jar is now a multi-release jar to provide implementations of Java 9 specific classes. Multi-release jars are not supported by the OSGi specification so OSGi modules will not be able to take advantage of these implementations but will not lose functionality as they will fall back to the implementations used in Java 7 and 8. More details on the new features and fixes are itemized below. Note that some tools are not compatible with multi-release jars and may fail trying to process class files in the META-INF/versions/9 folder. Those errors should be reported to the tool vendor.

During testing of the release it was found that one unit test fails when run on Windows. When building from source either use “mvn clean install -DskipTests” on Windows or run the build on a different operating system. The unit test failure is a problem in the test, not in Log4j. As always, pre-built distributions can be downloaded from http://www.apache.org/dist/logging/log4j/ or the binaries jars may be obtained from the Maven central repository.

[Read More]

Friday September 22, 2017

Log4j 2.9.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.9.1 release! This release primarily contains bugfixes and minor enhancements. [Read More]

Thursday August 31, 2017

Log4j 2.9 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.9 release!

This release contains the first support of Java 9 as well as bugfixes and minor enhancements. The Log4j API was modified to use java.util.ServiceLoader to locate Log4j implementations, although the former binding mechanism is still supported. The Log4j jar is now a multi-release jar to provide implementations of the Java 9 specific classes. Multi-release jars are not supported by the OSGi specification so OSGi modules will not be able to take advantage of these implementations but will not lose functionality as they will fall back to the implementations used in Java 7 and 8. More details on the new features and fixes are itemized below.

Note that subsequent to the 2.9 release, for security reasons, SerializedLayout is deprecated and no longer used as default in the Socket and JMS appenders. SerializedLayout can still be used as before, but has to be specified explicitly.

[Read More]

Saturday April 08, 2017

Log4j 2.8.2 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.8.2 release! This release primarily contains bugfixes and minor enhancements. [Read More]

Friday March 03, 2017

Log4j 2.8.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.8.1 release! This release primarily contains bugfixes and minor enhancements. [Read More]

Friday January 27, 2017

Log4j 2.8 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.8 release! This release contains several bugfixes and new features. The new features include the ability to have the RollingFileAppender log directly to the archive files, a new Apache Cassandra appender, a new ThreadContext::getThreadContextMap API method for custom ThreadContext implementations, support for variables in GelfLayout's additional fields, and support for Lookups in properties' default values. Also, this release continues the GC-free epic by updating many more filters and pattern layout converters so that they no longer allocate temporary objects during steady state logging. More details on the new features and fixes are itemized below. [Read More]

Tuesday October 11, 2016

A few more details about Apache Log4j 2.7

Here’s are the highlights of what’s new since Apache Log4j 2.6.2.[Read More]

Sunday July 17, 2016

Moving on to Log4j 2: Log4j 1.2 is broken on Java 9

Log4j 1 has had a good run. First released in 1999, it is still widely used in a variety of Java-based projects. With Java 9, that is likely to come to an end: Log4j 1.2 is broken on Java 9. Essentially the MDC depends on the Java version string, which does not play well with Java 9's new version-string format.

To any project that is interested in running on Java 9, I'd strongly recommend migrating to Log4j 2 now.

[Read More]

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation