Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Description
Currently starting the server with any JMX remoting system properties causes a ClassNotFoundException: org.apache.logging.log4j.jul.LogManager
because the JMX server connector initializes JDK logging before the Log4j classes are available.
JMX remoting configuration could also be simplified by using the default security realm to validate credentials and supplying authorization roles.
Attachments
Issue Links
- is depended on by
-
JDG-4726 ClassNotFoundException: org.apache.logging.log4j.jul.LogManager when we enable JMX
- Closed