> 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: Adding test to validate using DiagnosticCommand MBean to invoke AOT.end_recording ------------- Changes: - all: https://git.openjdk.org/jdk/pull/28010/files - new: https://git.openjdk.org/jdk/pull/28010/files/d48a200f..bff7cb74 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=28010&range=04 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=28010&range=03-04 Stats: 129 lines in 1 file changed: 129 ins; 0 del; 0 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
