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) ------------- Depends on: https://git.openjdk.org/jdk/pull/27965 Commit messages: - Removed whitespace - Removed extra functionality - 8369736 - Adding HotSpotAOTCache MXBean Changes: https://git.openjdk.org/jdk/pull/28010/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=28010&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8369736 Stats: 341 lines in 9 files changed: 338 ins; 0 del; 3 mod Patch: https://git.openjdk.org/jdk/pull/28010.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/28010/head:pull/28010 PR: https://git.openjdk.org/jdk/pull/28010
