The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Running NetBeans tests with JDK 7u17 reveals a deadlock in LogManager. See the attached dump.
See related NetBeans bug at
verified in b92
Based on the nightly test run results SQE is OK to take the fix into the June CPU.
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.
original changeset commit record :
HG Updates added a comment - 2013-04-20 07:27
Date: 2013-04-20 06:24:29 +0000
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.
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...
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.