JDK-8196361 : JTReg failure: serviceability/sa/ClhsdbInspect.java
- Type: Bug
- Component: hotspot
- Sub-Component: svc-agent
- Affected Version: 11
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: linux
- CPU: generic
- Submitted: 2018-01-29
- Updated: 2018-02-22
- Resolved: 2018-02-06
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 11 |
|---|
11 b01Fixed  |
Related Reports
|
Relates :
|
Description
This test fails on an AArch64 system (not necessarily unique to this platform, however) while looking for the line "waiting to re-lock in wait" in reference to the object java/lang/ref/ReferenceQueue$Lock. This line never appears in the output and instead it seems the object referred to has the line "waiting to lock" associated with it instead. The way the test is currently written there is not a straightforward way to tell the test to look for "waiting to lock" in reference to java/lang/ref/ReferenceQueue$Lock, as it finds "waiting to lock" in reference to java/lang/Class first.