1 Reply Latest reply on Sep 5, 2019 8:33 AM by pmm

    JBoss LogManager no longer configures system loggers correctly

    pmm
    pmm Sep 4, 2019 12:45 AM

      After migrating to Java 11 we were suddenly seeing a lot of caught exceptions in sun.rmi.runtime.Log#getSource(), see https://bugs.openjdk.java.net/browse/JDK-8230058.

       

      Apparently somewhere in Java 9 a distinction between system loggers and user loggers was introduced. See java.util.logging.Logger.SystemLoggerHelper

       

      The WildFly logging subsystem / JBoss LogManager seems to only configure user loggers but not not system loggers. This has the effect that the "sun.rmi" loggers run with level INFO rather than WARN and exceptions in Log#getSource() are thrown.

       

      How to reproduce the issue:

       

      1. download a stock WildFly 17.0.1.Final
      2. verify the "sun.rmi" log category is set to "WARN", this is the default
      3. start the WildFly without any deployment with --debug
      4. attach a remote debugger
      5. set a breakpoint in sun.rmi.runtime.Log#getSource()
      6. attach Java Mission Control and open the "MBean Server"
      7. you should hit the breakpoint and see the logger level is ALL instead of WARN