Integrated: 8269225: JFR.stop misses the written info when the filename is only specified by JFR.start

[Denghui Dong]

On Wed, 23 Jun 2021 09:34:05 GMT, Denghui Dong <ddong at openjdk.org> wrote:

> Hi,
> 
> Could I have a review of this small fix?
> 
> JFR.stop misses the written info when the filename is only specified by JFR.start, for example:
> 
> $jcmd 87802 JFR.start name=test filename=2.jfr
> 87802:
> Started recording 1. No limit specified, using maxsize=250MB as default.
> 
> Use jcmd 87802 JFR.dump name=test to copy recording data to file.
> 
> $jcmd 87802 JFR.stop name=test
> 87802:
> Stopped recording "test".
> 
> 
> The 'JFR.stop' didn't print written info, but actually, 2.jfr was generated.

This pull request has now been integrated.

Changeset: fd43d9cb
Author:    Denghui Dong <ddong at openjdk.org>
Committer: Yi Yang <yyang at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/fd43d9cb40f7e4b0f5ebc490e0490a222b8f2770
Stats:     55 lines in 2 files changed: 54 ins; 1 del; 0 mod

8269225: JFR.stop misses the written info when the filename is only specified by JFR.start

Reviewed-by: egahlin

-------------

PR: https://git.openjdk.java.net/jdk/pull/4573