JDK-8166208 : FlightRecorderOptions settings for defaultrecording ignored.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 8u102
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-09-16
  • Updated: 2018-02-07
  • Resolved: 2016-10-04
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 8
8u112Fixed
Description
After upgrading from Java 7u95 to 8u102 object allocation metrics are missing
from JFR recordings when settings=profile is used. The issue exists on
Solaris but Windows works just fine. The issue is easily repeatable using a
standalone JVM (simply jconsole w/JFR enabled via
-XX:+UnlockCommercialFeatures -XX:+FlightRecorder
-XX:FlightRecorderOptions=defaultrecording=true,disk=true,maxage=90m,stackdepth=512,settings=profile). 

The issue appears to be an issue w/the JVM and not the
configuration/profile.jfc file as I can successfully obtain object allocation
metrics on Solaris using a 7u95 JVM with a profile.jfc file taken from an
8u102 installation, however, the reverse fails (an 8u102 JVM with a
profile.jfr taken from 7u95 does not collect object allocation metrics). 

For example:
* JDK 8u102 with the profile.jfr from 8u102 - object allocations stats are missing
* JDK 7u95 with the profile.jfr from 7u92 - object allocations stats are there
* JDK 8u102 with the profile.jfr from 7u92 - oject allocation stats are missing
* JDK 7u95 with the profile.jfr from 8u102 - object allocations are there
Comments
Marking as 9-na, as I understand -XX:FlightRecorderOptions can lo longer be used to provide settings.
05-10-2016
Fix in progress. This has been added before in 8034045, to pass settings to the default recording, but that was disrupted in the 8u40 timeframe.
27-09-2016