ppkarwasz commented on PR #2775: URL: https://github.com/apache/logging-log4j2/pull/2775#issuecomment-2255891611
I ran a couple of tests on a simple JLink project to find out that: * the HotSpot JVM always loads `java.management` if it is present (the module provides an implementation of a `LoginModule` service that is consumed by `java.base`), so setting `java.management` as `static` should not cause problems to existing users: the module will be present at runtime anyway. * `AsyncLoggerDisruptor` and `AsyncLoggerConfigDisruptor` work correctly even if `java.management` is **missing**, so there is nothing to document there. I think, however, that we should **document** that setting `log4j2.jmxDisabled` to `false` requires JPMS users to add `java.management` to their module dependencies, otherwise JLink projects will fail to include it. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
