You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ppkarwasz (via GitHub)" <gi...@apache.org> on 2025/07/13 12:45:04 UTC
Re: [PR] Make `StatusLogger` self-contained and testable [logging-log4j2]
ppkarwasz commented on PR #2249:
URL: https://github.com/apache/logging-log4j2/pull/2249#issuecomment-3067027459
Hi @vy,
It looks like this change isn't mentioned in the [2.23.0 release notes](https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-23-0), even though—if I recall correctly—it was one of the most significant enhancements in that version.
Notably, this change has an important (and, as I remember it, intentional) side effect for users of `log4j-to-slf4j` and `log4j-to-jul`: it disables message pooling via `ReusableMessageFactory`. This behavior aligns with the design of the target logging systems:
* The default JUL implementation lacks GC-free features, and JBoss LogManager provides its own optimized `log4j-to-jul` integration.
* Logback, the only native SLF4J implementation, also creates a new `LoggingEvent` object per log call.
So, disabling GC-free logging in these bridges was a deliberate decision—but one that should be clearly documented. Could you please update the release notes to reflect this?
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org