[left] The JVMTM tool interface (JVM TI) is a native programming interface for use by tools. It provides both a way to inspect the state and to
control the execution of applications running in the JavaTM virtual machine (JVM). JVM TI supports the full breadth of tools that need
access to JVM state, including but not limited to: profiling, debugging, monitoring, thread analysis, and coverage analysis tools.
Note: JVM TI was introduced at JDKTM 5.0. JVM TI replaces the Java Virtual Machine Profiler Interface (JVMPI) and the Java Virtual Machine
Debug Interface (JVMDI) which, as of JDK 6, are no longer provided.
JVM TI Reference
* See the JVM TI Reference for overview, API reference, and usage information.
API Enhancements
* See the API Enhancements in JDK 6 - An annotated list of API changes between the 5.0 and 6 releases.
More Information
* Java Virtual Machines - features, command-line options, and additional information.
* Java Native Interface - the interface which JVM TI extends.
* java.lang.instrument package - a Java programming language alternate to JVM TI if only the instrumentation
functionality of JVM TI is used.
* As used on this web site, the terms "Java Virtual Machine" or "JVM" mean a virtual machine for the Java
platform.
[/left]
FATAL ERROR: JVMPI, an experimental interface, is no longer supported.
Please use the supported interface: the JVM Tool Interface (JVM TI).
For information on temporary workarounds contact: jvmpi_eol@sun.com
For a long time now, since we released JDK 1.5, we have been warning people that the VM profiling interface
JVMPI is going away. Starting with the JDK 6 update 3 release (JDK6u3), it is gone for good.
If you really need JVMPI, your best bet is to use a JDK 1.5 or older release, and also find out about transitioning
to JVM TI. More often than not, you have become dependent on a tool that uses JVMPI, in which case you should
try and upgrade that tool to a version that uses JVM TI instead. But if you have written your own JVMPI code, see
the JVMPI transition article at 0bdK9s2c8@1M7q4)9K6b7g2)9J5c8W2)9J5c8X3A6S2N6X3q4Q4x3X3g2K6N6h3&6Q4x3X3g2U0L8$3#2Q4x3V1k6V1k6i4k6W2L8r3!0H3k6i4u0Q4x3V1k6@1k6h3y4Z5L8X3W2U0j5h3I4m8M7Y4c8A6j5$3I4W2M7#2)9J5c8W2m8J5L8$3N6J5j5h3#2E0K9h3&6Y4i4K6u0r3K9Y4k6E0M7r3W2@1M7X3q4F1M7$3W2@1K9h3!0F1i4K6u0r3 for
help in transitioning to JVM TI.
NOTE: Getting this message indicates that JVMPI has been requested of the JVM. A request for JVMPI must be made
prior to JVM initialization and regardless of whether JVMPI is eventually used at runtime, just the request for it will
have a negative performance impact on your Java application. In most situations, JVMPI should never be requested
unless some kind of performance work is being done and slower performance is considered acceptable. JVM TI does
not have many of the JVMPI limitations.[/left]
