On Wed, 29 Oct 2025 21:07:51 GMT, Mat Carter <[email protected]> wrote:
>> Add jdk.management.AOTCacheMXBean. The interface provides a single action >> that when called will cause any hosted JVM currently recording AOT >> information will stop recording. Existing functionality is preserved: when >> stopped the JVM will create the required artifacts based on the execution >> mode. Conveniently as the application running on the JVM has not stopped (as >> was previously the only way to stop recording), the application will resume >> execution after the artifacts have been generated. >> >> The interface will return TRUE if a recording was successfully stopped, in >> all other cases (not recording etc.) will return FALSE >> >> It follows that invoking the action on a JVM that is recording, twice in >> succession, should (baring internal errors) produce the following two >> responses: >> >> TRUE >> FALSE >> >> Passes tier1 on linux (x64) and windows (x64) > > Mat Carter has updated the pull request incrementally with one additional > commit since the last revision: > > Updated test based on comments Can this be done using a diagnostic command, e.g. AOT.stop? It would allow the recording to be stopped from jcmd and the DiagnosticCommandMBean, without the need for a separate MXBean. ------------- PR Comment: https://git.openjdk.org/jdk/pull/28010#issuecomment-3480099956
