JDK-4914266 : Remove JVMPI in Dolphin/JDK7/Java7
  • Type: Enhancement
  • Component: vm-legacy
  • Sub-Component: jvmpi
  • Affected Version: 6
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-08-28
  • Updated: 2017-05-16
  • Resolved: 2007-05-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u4Fixed 7Fixed hs10Fixed
Related Reports
Duplicate :  
JDK-6513560 - Remove suggestion to mail jvmpi_eol from fatal error message
Relates :  
JDK-6387310 - include/jvmpi.h is missed
Relates :  
JDK-6913186 - a number of vm tests failed against jdk 5.0 with HS 16 nightly build
Relates :  
JDK-4639363 - Java Platform Profiling Architecture (JSR-163)
Relates :  
JDK-6265756 - Remove JVMDI
Relates :  
JDK-6533127 - fix for 4914266 reveals CHECK_UNHANDLED_OOPS compilation problems
Description
JVMTI developed under JSR-163 and to be released under J2SE 1.5 was designed
as a replacement for JVMPI.  The members of the Expert Group felt that one
major release cycle (that is 1.6) was sufficent to convert tools based on JVMPI.

JVMTI is basically an enhanced JVMDI, so JVMDI is no longer needed. To our 
knowledge the only products based on JVMDI are Sun's -- the JPDA back-end (which
has already been converted to JVMTI) and jdbx.  JVMDI has also been used in 
some university research projects.

Maintaining JVMPI and JVMDI in the VM is a significant maintenance burden,
as the VM changes there interfaces break.  Their presence complicates the
VM code.  And finally, even when off, JVMPI has a performance impact.
Comments
SUGGESTED FIX The proposed fix for phase 3 has been resynced after the undef-ws was putback to main/baseline and is attached as 4914266-remove-webrev-cr1.tgz.
05-04-2007
SUGGESTED FIX The PRT/PIT builds of the undef workspace revealed the need for a couple more platform specific #ifdef's. The deltas were sent out for code review round 2 . The deltas are attached as 4914266-ifdef-webrev-cr2.tgz.
23-03-2007
SUGGESTED FIX The initial proposed fix for phase 3 is attached as 4914266-remove-webrev-cr0.tgz.
22-03-2007
SUGGESTED FIX The initial proposed fix for phase 2 is attached as 4914266-undef-webrev-cr0.tgz.
22-03-2007
SUGGESTED FIX The original proposed fix was modified as a result of code review round 0 and the deltas were sent out for code review round 1 and approved. The deltas are attached as 4914266-ifdef-webrev-cr1.tgz.
21-03-2007
SUGGESTED FIX The initial proposed fix for phase 1 is attached as 4914266-ifdef-webrev-cr0.tgz.
15-03-2007
SUGGESTED FIX phase 0 - Create switch to enable JVM/PI The switch was created in Mustang-B16 with a default value of true. The switch default was changed to false in Mustang-B19. As of B19, JVM/PI no longer works without special intervention. phase 1 - Identify all JVM/PI code with #ifdef JVMPI_SUPPORT ... #endif. JVMPI_SUPPORT is defined by default so no change in functionality. phase 2 - Remove #define JVMPI_SUPPORT which means that JVM/PI is no longer built by default. phase 3 - Remove JVM/PI code identified by #ifdef JVMPI_SUPPORT ... #endif.
27-02-2007
EVALUATION JVMDI was removed by the child CR 6265756 ###@###.### 2005-05-11 07:17:27 GMT JVM/PI will be removed early in Dolphin.
19-10-2005
EVALUATION JVMPI and JVMDI should be removed in J2SE 1.6
11-06-2004
SUGGESTED FIX Remove them
11-06-2004
PUBLIC COMMENTS JVMTI developed under JSR-163 and to be released under J2SE 1.5 was designed as a replacement for JVMPI. The members of the Expert Group felt that one major release cycle (that is 1.6) was sufficent to convert tools based on JVMPI. JVMTI is basically an enhanced JVMDI, so JVMDI is no longer needed. To our knowledge the only products based on JVMDI are Sun's -- the JPDA back-end (which has already been converted to JVMTI) and jdbx. JVMDI has also been used in some university research projects. Maintaining JVMPI and JVMDI in the VM is a significant maintenance burden, as the VM changes there interfaces break. Their presence complicates the VM code. And finally, even when off, JVMPI has a performance impact.
10-06-2004