JDK-8027670 : DeadLock in drainLoggerRefQueueBounded / readConfiguration
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 8
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2013-10-31
  • Updated: 2014-01-16
  • Resolved: 2013-11-27
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Thread 1:
    at
java.util.logging.LogManager.drainLoggerRefQueueBounded(LogManager.java:816)
       - waiting to lock <0x1b260998> (a java.util.logging.LogManager)
       at java.util.logging.LogManager.addLogger(LogManager.java:852)
       at java.util.logging.LogManager.demandLogger(LogManager.java:398)
       at
java.util.logging.LogManager$LoggerContext.demandLogger(LogManager.java:478)
       at
java.util.logging.LogManager$LoggerContext.processParentHandlers(LogManager.java:604)
       at
java.util.logging.LogManager$LoggerContext.addLocalLogger(LogManager.java:540)
       - locked <0x1b266518> (a java.util.logging.LogManager$LoggerContext)
       at java.util.logging.LogManager.addLogger(LogManager.java:854)
       at java.util.logging.LogManager.demandLogger(LogManager.java:398)
       at java.util.logging.Logger.demandLogger(Logger.java:352)
       at java.util.logging.Logger.getLogger(Logger.java:399)

Thread 2:
at
java.util.logging.LogManager$LoggerContext.findLogger(LogManager.java:482)
       - waiting to lock <0x1b266518> (a
java.util.logging.LogManager$LoggerContext)
       at
java.util.logging.LogManager.setLevelsOnExistingLoggers(LogManager.java:1362)
       - locked <0x1b260998> (a java.util.logging.LogManager)
       at
java.util.logging.LogManager.readConfiguration(LogManager.java:1121)

Comments
This is now covered by JDK-8029281
27-11-2013

This looks like a duplicate of JDK-8010939. I haven't been able to reproduce the deadlock on 8 - although it looks as if there's still a possibility for it to happen. Still investigating.
18-11-2013