JDK-8029281 : Synchronization issues in Logger and LogManager
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.logging
- Affected Version: 8
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-11-27
- Updated: 2014-10-15
- Resolved: 2013-12-04
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 |
|---|---|
7u60Fixed  |
8 b120Fixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
LogManager and Logger have several synchronization issues which are causing intermittent test and application failures. These issues are inter related and need to be fixed in a coherent way. For instance JDK-8029092 shows two tests failures which points at possible synchronization issues outlined in JDK-8028763 - as well as to an issue in the way the Logger tree is cleaned up when Loggers are garbage collected. Fixing it will therefore require to touch at drainLoggerRefQueueBounded(), which cannot be done without taking JDK-8027670 into account.
Comments
|