This is an automated email from the ASF dual-hosted git repository. vy pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
commit 7fbb96bd7a30b8cbee94b2d5a70e38aa885346eb Author: Volkan Yazıcı <[email protected]> AuthorDate: Tue Jul 2 09:54:00 2024 +0200 Improve `garbagefree.adoc` on property substitutions --- src/site/antora/modules/ROOT/pages/manual/garbagefree.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/site/antora/modules/ROOT/pages/manual/garbagefree.adoc b/src/site/antora/modules/ROOT/pages/manual/garbagefree.adoc index 7d0973019f..98dadb5f52 100644 --- a/src/site/antora/modules/ROOT/pages/manual/garbagefree.adoc +++ b/src/site/antora/modules/ROOT/pages/manual/garbagefree.adoc @@ -239,10 +239,9 @@ If pool runs out of capacity (see <<log4j.recycler.capacity>>), it will start cr There are certain caveats associated with the configuration of garbage-free logging: [#core-limitation-properties] -`<Properties>` section:: +Property substitutions:: -A configuration containing xref:manual/configuration.adoc#property-substitution[a `<Properties>` section] will result in temporary -objects being created during steady-state logging. +Some xref:manual/configuration.adoc#PropertySubstitution[property substitutions] (e.g., ones using xref:manual/lookups.adoc#DateLookup[Date Lookup]) might result in temporary objects being created during steady-state logging. [#core-limitation-async-logger-wait-strategy] Asynchronous logger wait strategies::
