JDK-8031980 : Add new j.u.l deadlock test for JDK-8027670 and JDK-8029281
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.logging
- Affected Version: 8
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-01-16
- Updated: 2015-01-06
- Resolved: 2014-01-21
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.
To download the current JDK release, click here.
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.
To download the current JDK release, click here.
| JDK 7 | JDK 8 | JDK 9 |
|---|---|---|
7u60Fixed  |
8u20Fixed |
9 b02Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The test test/java/util/logging/TestLogConfigurationDeadLock.java attempts to detect deadlocks for JDK-8027670 and JDK-8029281, but passes always whether the fix is present or not. Recent sighting of JDK-8027670 have shown that obtaining the deadlock is much frequent when creating a new logger whose parent does not exists yet, but has a level defined in the j.u.l config file. A new test somewhat similar to TestLogConfigurationDeadLock - but using a configuration file defining levels for parent loggers should be added to obtain more testing coverage for the deadlock shown in JDK-8027670.
Comments
|