Log4j 2 is nominated for the JAX Innovation Awards!
Do you like its performance, garbage-free logging, and easy and flexible configuration?
Log4j 2 needs your love. Vote for Log4j 2!
On August 5, 2015 the Logging Services Project Management Committee announced that Log4j 1.x had reached end of life. For complete text of the announcement please see the Apache Blog. Users of Log4j 1 are recommended to upgrade to Apache Log4j 2.
Apache log4j 1.2.17 is distributed under the Apache License, version 2.0.
The link in the Mirrors column should display a list of available mirrors with a default selection based on your inferred location. If you do not see that page, try a different browser. The checksum and signature are links to the originals on the main distribution server.
|Apache log4j 1.2.17 (tar.gz)||log4j-1.2.17.tar.gz||log4j-1.2.17.tar.gz.md5||log4j-1.2.17.tar.gz.asc|
|Apache log4j 1.2.17 (zip)||log4j-1.2.17.zip||log4j-1.2.17.zip.md5||log4j-1.2.17.zip.asc|
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases.
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using
% gpg --import KEYS % gpg --verify log4j-1.2.17.tar.gz.asc
Apache log4j 1.2.17 is signed by Christian Grobmeier 42196CA8
Alternatively, you can verify the MD5 signature on the files. A unix program called md5 or md5sum is included in many unix distributions.
All previous releases of Apache log4j can be found in the archive repository.