2.12.1
- Release date
-
2019-08-06
This release contains bugfixes and minor enhancements.
This release improves the performance of capturing location information, makes log4j-core
optional in the log4j 1.2 bridge, and explicitly removes LoggerContext
references from components that keep track of them when the LoggerContext is shut down.
More details on the new features and fixes are itemized below.
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.12.1 API, as well as many core components, maintains binary compatibility with previous releases.
Log4j 2.12.1 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.
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.
Changed
-
Make Log4j Core optional for Log4j 1.2 API. (LOG4J2-2556)
-
Update MongoDB 3 driver from 3.10.1 to 3.10.2. (LOG4J2-2646)
-
Improve exception messages in the JDBC appender. (LOG4J2-2657)
-
Retry when JDBC throws a java.sql.SQLTransactionRollbackException in commitAndClose(). (LOG4J2-2660)
Fixed
-
Allow file renames to work when files are missing from the sequence. (LOG4J2-1946)
-
Remove references to LoggerContext when it is shutdown. (LOG4J2-2366)
-
Improve the performance of capturing location information. (LOG4J2-2644)
-
Support emulating a MAC address when using ipv6. (LOG4J2-2650)
-
AbstractAction.reportException records a warning to the status logger, providing more information when file based appenders fail to compress rolled data asynchronously. (LOG4J2-2658)
-
AbstractAction handles and records unchecked RuntimeException and Error in addition to IOException. (LOG4J2-2659)
-
"Values not bound to statement" when using JDBC appender, appender does not respect bufferSize="0". (LOG4J2-2667)