ppkarwasz commented on issue #2895: URL: https://github.com/apache/logging-log4j2/issues/2895#issuecomment-2314864992
After discussing it with @vy, I am closing this issue as `not-planned`, since: - JMX support will be disabled by default in `2.24.0`. - JMX support is deprecated. - Fixing this issue requires major changes in the JMX support code. **Note**: If somebody wants to fix this, please take into consideration that: - JMX initialization needs to occur on a background thread to prevent the deadlock. - The `Server` class already has a background thread that is used for JMX notification. However the thread is disabled in web applications (see [LOG4J2-938](https://issues.apache.org/jira/browse/LOG4J2-938)). Using the asynchronous thread for all types of applications requires an alternative solution to `LOG4J2-938`. - JUnit 5 already recommends disabling JMX in tests (see https://github.com/junit-team/junit5/pull/3753). -- 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]
