Agent Controller - release notes


1.0 Known problems
   1.1 Mismatched location of "libjvm.sl" on HP-UX causes Leak Analysis to fail

1.0 Known problems

1.1 Mismatched location of "libjvm.sl" on HP-UX causes Leak Analysis to fail

When using the "Memory Leak Analysis - Manual heap dumps" or "Memory Leak Analysis - Timed heap dumps" profiling feature on an application running on HP-UX, you may see the following error dialog:

 "Leak Analysis validation failed. Check that the Agent Controller is running"

If this happens when Agent Controller is already running on the target HP-UX host, search the config/servicelog.log in your HP-UX Agent Controller installation directory for a warning message with the text:

 "Could not create file server because JVM could not be created"

This problem can occur when using Memory Leak Analysis with the HP JVM on PA-RISC 2.0 hosts. To work around the problem, edit the config/serviceconfig.xml in your HP-UX Agent Controller installation directory. Locate the line that begins "<AgentControllerConfiguration". Within this line, locate the path to libjvm.sl. For example, if your JRE is installed in /opt/java1.4, you would see:

<AgentControllerConfiguration activeConfiguration="default" filePort="10005" jvm=/opt/java1.4/jre/lib/PA_RISC/server/libjvm.sl" ...

Modify the path to libjvm.sl to refer to your_jre/jre/lib/PA_RISC2.0 instead of PA_RISC. The above example would become:

<AgentControllerConfiguration activeConfiguration="default" filePort="10005" jvm=/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl" ...

Save your changes, then stop and restart Agent Controller on your HP-UX host. If the file server creation warning does not recur in your servicelog.log, Leak Analysis should now work properly.

Note: If you reconfigure your HP-UX Agent Controller by running SetConfig.sh, serviceconfig.xml will be overwritten and you will need to make this modification again.

Return to the main readme file