JDK-8212232 : Wrong metadata for the configuration of the cutoff for old object sample events
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jfr
  • Affected Version: 10,11,12
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-10-16
  • Updated: 2020-04-27
  • Resolved: 2018-12-07
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 11 JDK 12 Other
11.0.3-oracleFixed 12 b24Fixed openjdk8u262Fixed
Related Reports
Blocks :  
JMC-6141 - JMC logs warnings when creating recordings
Relates :  
JDK-8239140 - Backport JFR to OpenJDK 8
Description
The composite data containing the metadata for the old object samples cutoff show the cutoff to be jdk.jfr.BooleanFlag, when it should probably be jdk.jfr.Timespan.
Comments
Replacing jdk8u-fix-request with link to JDK-8239140
17-02-2020
RFC: https://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-January/011063.html
30-01-2020
Fix Request: This fix for JFR should be downported to jdk11u to avoid inconsistencies with current versions. It applies cleanly. Will run tests before pushing to jdk11u.
18-02-2019
Any chance this could be fixed in a JDK 11 update? The fix is easy and safe. The metadata problem causes errors in the JMC logs every time a recording is started, as infinity is not a valid boolean value.
16-10-2018
I think it has always been broken.
16-10-2018
Is this a regression from JDK 10? Or has it always been broken.
16-10-2018