JDK-8322675 : JFR: Fail-fast mode when constants cannot be resolved
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jfr
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-12-22
  • Updated: 2024-01-23
  • Resolved: 2024-01-16
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.
JDK 23
23 b06Fixed
Related Reports
Relates :  
JDK-8323883 - JFR AssertionError: Missing object ID 15101
Description
A reoccurring problem in JFR are constants, i.e. threads, classes and methods, not being resolved properly. Users will see this as a field value being null (N/A), or NPE if application code depends on the value not being null. 

Today, we can track those occurrences with -Xlog:jfr+system+parser=info, but if we had a fail-fast mode enabled during testing, we would find the problem closer to when it's introduced.

It could be an assert, or a system property, that is checked and an InternalError is thrown if an unresolvable value is found.
Comments
Changeset: 21f64731 Author: Erik Gahlin <egahlin@openjdk.org> Date: 2024-01-16 13:59:29 +0000 URL: https://git.openjdk.org/jdk/commit/21f647310b49a5002cec4742a1c6310d746ac211
16-01-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/17254 Date: 2024-01-03 20:45:06 +0000
03-01-2024