Re: [D] Extra logger lines in logs from log4j internal class after upgrade to version 2.25.3 [logging-log4j2]

vy (via GitHub) <[email protected]> Mon, 16 Feb 2026 10:25:22 -0000
Newsgroups gmane.comp.jakarta.log4j.devel
Message-ID <ghd-D_kwDOAKJSSM4Aj4BK-b11c0615-e266-44cd-8f97-d64560b3bb68__43617.3731389985$1771237531$gmane$org@gitbox.apache.org>
GitHub user vy added a comment to the discussion: Extra logger lines in logs from log4j internal class after upgrade to version 2.25.3

@bimlesh111, would you mind sharing your Log4j configuration file and the Log4j configuration system properties you pass to your application, please?

I guess you have one or more of the following:

1. [The `status` configuration attribute](https://logging.apache.org/log4j/2.x/manual/configuration.html#configuration-attribute-status) in your Log4j configuration file
2. The `log4j2.defaultStatusLevel` configuration property (or the associated environment variable)
3. [The `log4j2.statusLoggerLevel` configuration property](https://logging.apache.org/log4j/2.x/manual/status-logger.html#log4j2.statusLoggerLevel) (or the associated environment variable)
4. [The `log4j2.debug` configuration property](https://logging.apache.org/log4j/2.x/manual/status-logger.html#log4j2.debug) (or the associated environment variable)

See [Status Logger](https://logging.apache.org/log4j/2.x/manual/status-logger.html) for details.

GitHub link: https://github.com/apache/logging-log4j2/discussions/4040#discussioncomment-15822273

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]