This is an automated email from the ASF dual-hosted git repository. rpopma pushed a commit to branch release-2.x in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/release-2.x by this push: new 448b057cf0 LOG4J2-3473 (DOC) fix version number 448b057cf0 is described below commit 448b057cf0a938a102be9cd9fe540831e3751ce9 Author: Remko Popma <rem...@yahoo.com> AuthorDate: Wed Apr 27 14:41:11 2022 +0900 LOG4J2-3473 (DOC) fix version number fix version number when default waitstrategy is garbage-free --- src/site/xdoc/manual/garbagefree.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/xdoc/manual/garbagefree.xml b/src/site/xdoc/manual/garbagefree.xml index 6f68a37673..1d20a4d349 100644 --- a/src/site/xdoc/manual/garbagefree.xml +++ b/src/site/xdoc/manual/garbagefree.xml @@ -111,7 +111,7 @@ will result in temporary objects being created during steady-state logging. </p> <p> - <b>Note 2:</b> as of version 2.17.3, the default Async Logger wait strategy used by Log4j + <b>Note 2:</b> as of version 2.18.0, the default Async Logger wait strategy used by Log4j (Timeout) is garbage-free. Some of the wait strategies included in LMAX disruptor 3.4.4, especially <tt>TimeoutBlockingWaitStrategy</tt> and <tt>BlockingWaitStrategy</tt> (Block) are not garbage-free since they