To ensure thread-safe initialization, the constructor of JDK14LoggerFactory invokes (line 47) java.util.logging.LogManager.getLogManager() . I don't understand how this call can fail but not a call to JDK14LoggerFactory.getLogger() which invokes LogManager.getLogManager() indirectly.
As far as I can tell, the only relevant difference between 1.7.19 and earlier versions is that the call to LogManager.getLogManager() is made sooner (within SLF4J initialization) which seems perfectly legitimate and not a bug.
Osvaldo Pinali Doederlein Could you please check that removing the LogManager.getLogManager() call in the constructor of JDK14LoggerFactory fixes the issue?
|