RFR: 8351146: JFR: JavaMonitorInflate event should default to no threshold and be disabled [v2]

[Erik Gahlin]

On Fri, 7 Mar 2025 12:57:55 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

> This makes sense. I guess this is better than leaving it as 20 and having someone know to change it to 0 in their jfc file. Is there a command line way to enable the event, or does that require a custom jfc file?

That's true, with a 20 ms threshold, users can specify -XX:StartFlightRecording:locking-threshold=0ms to enable the event, which may be easier than -XX:StartFlightRecording:jdk.JavaMonitorInflate#enabled=true.

That said, if the duration/threshold is useless, I think it's a good idea to remove it. I would assume that few users set locking-threshold=0ms anyway, as it results in an enormous amount of events, not just JavaMonitorInflate.

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

PR Comment: https://git.openjdk.org/jdk/pull/23891#issuecomment-2706794728