Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in Logback while fixing some inherent problems in Logback's architecture.
Some of the features and improvements in Log4j 2 are:
The API for Log4j is separate from the implementation. It is now clear to application developers what classes and methods they can use with compatibility being assured while allowing improvements to be made to the implementation.
Faster performance than Log4j 1.x in critical areas and similar performance to Logback in most circumstances. See Performance for more information.
While the Log4j 2 API will provide the best performance, support for the SLF4J and Commons Logging APIs are provided.
Like Logback, Log4j 2 can automatically reload its configuration upon modification. Unlike Logback, it will do so without losing log events while reconfiguration is taking place.
Like Logback, Log4j 2 supports filtering based on context data, markers, regular expressions and other components in the Log event and can be specified to apply to all events before being passed to Loggers or as they pass through appenders. In addition, filters can also be associated with Loggers. Unlike Logback, a common Filter class can be used in any of these circumstances.
All configurable components are defined as Log4j plugins. As such, no Log4j code must be changed to create a new Appender, Layout, Pattern Converter, etc. Log4j will automatically recognize properly defined plugins and use them when they are referenced in the configuration.
Properties can be referenced in the configuration and either be directly replace or passed to the underlying component where they can be dynamically resolved. Properties can come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event. Users can further customize the property providers by adding their own Lookup Plugin.