The version 1.6.x JVM only supports the JVMTI 1.1 profiling interface and does not support the JVMPI profiling interface. The default profiling interface for DevPartner Java Edition is JVMTI 1.1. However, the 1.4.x JVM supports the JVMPI profiling interface but does not support the JVMTI 1.1 profiling interface. The version 1.5.x JVM supports the JVMPI profiling interface and JVMTI 1.0 profiling interface but does not support the JVMTI 1.1 profiling interface.
The following message may be encounterd when attempting to start a profiling session with a version 1.5.x JVM. DPJ: Using JVMTI 1.0.36 DPJ: JVMTI 1.0.36 is not supported. Please use a JVM that implements atleast JVMTI 1.1 The session has ended
It is possible to profile using the JVMPI profiling interface but the default confuguration for DevPartner for Java Edition must be modifed.
To change the default profing interface to JVMPI, locate the DPJ.conf file in C:\ProgramData\Micro Focus\DevPartner Java Edition\var\conf\DPJ.conf or C:\Documents and Settings\All Users\Application Data\var\conf
Comment out this strng, DPJ_CORE=dpjJvmtiCore Un-Comment out this string. DPJ_CORE=dpjCore
So that the file looks like this: # # DPJ configuration file # # Base port for NCS communications NCSP_PORT=21578 # DPJ UI server ports (must match server.xml) TOMCAT_PORT=21580 TOMCAT_AUX_PORT=21579 # DPJ version number DPJ_VERSION=4.5.0 (Build 1791) # DPJ core base name # DPJ_CORE=dpjJvmtiCore # DPJ core base name DPJ_CORE=dpjCore # DPJ instrumentation library base name DPJ_INSTR_LIBRARY=dpjJavaInstr # Number of threads in NCS thread pool NCSP_THREADS=5
Save the file. Then restart the ncsp service: 1. NET STOP NCSP NET START NCSP 2. Reboot.
To change the default profiling interface to JVMTI, reverse the above procedure.