JDK-8213015 : Inconsistent settings between JFR.configure and -XX:FlightRecorderOptions
- Type: Bug
- Component: hotspot
- Sub-Component: jfr
- Affected Version: 11,12
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-10-26
- Updated: 2020-04-27
- Resolved: 2018-11-23
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.4Fixed | 12 b22Fixed  |
openjdk8u262Fixed |
Related Reports
|
Relates :
|
Description
globalbuffersize, thread_buffer_size, memorysize, maxchunksize in -XX:FlightRecorderOptions can be set as "MEMORY SIZE" type. OTOH them in JFR.configure cannot be set so because they are defined as JLONG. Also default values between JFR.configure and -XX:FlightRecorderOptions are inconsistent - globalbuffercount and memorysize. They should be consistent.
Comments
|