Minor change in JFR file format

[Jason Fordham]

Hi Erik,

On 12/12/22 3:03 PM, Jason Fordham wrote:
> On 12/08/22, Erik Gahlin wrote:
>
>> We are considering bumping the minor version (a non-breaking change) of
>> the file format, but we are not sure if it is necessary as it was already
>> treated as a long value by the JMC parser?
>>
>> It's more of a problem for the JDK parser, it checks that the number of
>> bytes read matches that of the event size, but since it is already broken
>> for large check point events, a change will not make it more broken. See
>> this JDK bug for details:
>> https://bugs.openjdk.org/browse/JDK-8298129
>>
>> This change will not impact the size of ordinary events.

The customer involved has confirmed that they would like to be able to 
read their historical collection of JFRs using a single tool, and so a 
bump in the minor version number would make maintaining their automated 
tools easier going forward. I hope this information doesn't come too late.

Kind regards,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221214/332a8668/attachment-0001.htm>