United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-8010939 Deadlock in LogManager
JDK-8010939 : Deadlock in LogManager

Details
Type:
Bug
Submit Date:
2013-03-27
Status:
Closed
Updated Date:
2013-11-18
Project Name:
JDK
Resolved Date:
2013-04-24
Component:
core-libs
OS:
Sub-Component:
java.util.logging
CPU:
Priority:
P2
Resolution:
Fixed
Affected Versions:
7u13,7u17,8
Fixed Versions:

Related Reports
Backport:
Backport:
Backport:
Backport:
Backport:
Backport:
Backport:
Relates:

Sub Tasks

Description
Running NetBeans tests with JDK 7u17 reveals a deadlock in LogManager. See the attached dump.

See related NetBeans bug at
http://netbeans.org/bugzilla/show_bug.cgi?id=227981

                                    

Comments
URL:   http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/e8f1dc6d0c0c
User:  lana
Date:  2013-05-07 18:40:01 +0000

                                     
2013-05-07
GL 4.0 has just run into this deadlock in their upcoming July release. We'd like to make this fix available sooner since August release would be too late.
                                     
2013-05-09
Based on the nightly test run results SQE is OK to take the fix into the June CPU.
                                     
2013-05-13
verified in b92
                                     
2013-06-08
The broken code that deadlocks is result of following commit (into JDK8 tree):

6737:d1668eca22bf - mchung Nov 27, 2012
6664509: Add logging context
6664528: Find log level matching its name or value given at construction time
Reviewed-by: alanb, ahgross, jgish, hawtin

It is not present in JDK7_u07 - it has been backported later.
                                     
2013-04-03
According to JDK-8000542, the backport happened in 7u13. E.g. as a workaround for frequent deadlocks that NetBeans testing infrastructure is facing we can downgrade the JDK to anything older than 7u13...
                                     
2013-04-03
Skimmed on the deadlock stack trace and the call to manager.drainLoggerRefQueueBounded() should be moved out from LoggingContext.addLocalLogger to LogManager.addLogger after the null name check.
                                     
2013-04-12
original changeset commit record : 

HG Updates added a comment - 2013-04-20 07:27
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/e8f1dc6d0c0c
User: mchung
Date: 2013-04-20 06:24:29 +0000
                                     
2013-04-24



Hardware and Software, Engineered to Work Together