JDK-8209960 : -Xlog:jfr* doesn't work with the JFR parser
- Type: Bug
- Component: hotspot
- Sub-Component: jfr
- Affected Version: 11,12
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-08-24
- Updated: 2020-04-27
- Resolved: 2018-11-20
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 | JDK 12 | Other |
|---|---|---|
| 11.0.3-oracleFixed | 12 b19Fixed  |
openjdk8u262Fixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
The JFR parser (ChunkParser.java) has been instrumented with log statement to debug parser issues, for instance, information about the chunk header or contents of the constant pool types. The functionality has however stopped working The reason is that the jdk.jfr.internal.JVM class has not been initialized, so the log levels are not registered in the VM. The dependency on the JVM class was removed from the jdk.jfr.internal.Logger so that files could be parsed on a JVM that doesn't support JFR. We should add back the dependency, but in case we get UnsatisfiedLinkError loading the JVM klass we should fall back to no logging. The workaround is to debug the parser and start a recording on command-line at the same time: java -Xlog:jfr+parser+system -XX:StartFlightRecording ..
Comments
|