Created On:  2009-02-05

Problem:

There are cases in which a profiling session cannot be started on an Application Server from the DevPartner Java Edition User interface, and cannot be started using nmshell.

Resolution:

For JVMs 1.6.x that use the JVMTI profiling interface the –agentlib command can be used to launch a profiling session by adding the following argument (as one line) to the JVM settings:

-agentlib:dpjJvmtiCore=NM_ANALYSIS_TYPE={coverage,performance,memory}, | NM_CONFIG_NAME={name of DPJ Configuration},NM_BATCH={1}
Sample syntax is below:
java -agentlib:dpjJvmtiCore=performance, NM_CONFIG_NAME=test  [your other java options]

For an explanation of the various switches please consult the online help facility.