Check to see what Java version you are using. If you are running Java 1.4.2_07, try setting SHLIB_PATH, rather than using LD_LIBRARY_PATH to define the shared library location. If this doesn't work, you may need to update to a newer JDK.

•You can set a log level on the JVM agent, which lets you collect varying amounts of information about the console and JVM agent. For example:

$ /opt/java1.5/bin/java -Xms256m -Xmx512m -agentlib:jmeter=logging=level_of_detail

Available log levels:

—FINEST (most impact on performance)

—FINER

—FINE

—CONFIG

—INFO

—WARNING (default setting)

—SEVERE (least impact on performance)

Node agent

On HP-UX systems, the node agent may occasionally leave files in /var/opt/hpjmeter/ fifos, with names ending with *fifo. These files are used for node agent communication, and you should not remove them while a node agent or JVM agent is active. You can delete these files when the node agent is not running if they begin to accumulate.

•On HP-UX you may sometimes not be able to restart the node agent with the same port. If you stopped the node agent and then tried to run it again, you may see the following:

Can't use port port_number. Try using the -port option to select a port from 9505 to 9515.

To work around the problem, restart the node agent using a different port number.

If the problem with the un-terminated connections persists, you can reduce the frequency by using this command as root:

$ ndd -set /dev/tcp tcp_fin_wait_2_timeout 300000

This sets the timeout in milliseconds for the leftover connections. The example sets this timeout to 5 minutes (300000 milliseconds). After about five minutes, you should be able to restart the server using the same port number as before.

•You can set a log level on the node agent, which lets you collect varying amounts of information about the console and node agent. To set the log level, use this command to manually start a new node agent:

$ JMETER_HOME/bin/nodeagent -logging=level_of_detail

Available log levels:

—FINEST (most impact on performance)

—FINER

—FINE

—CONFIG

—INFO

—WARNING (default setting)

—SEVERE (least impact on performance)

For more information about the node agent, see Managing Node Agents (page 37).

Zero Preparation Profiling

We have suggested that you use -usr2to start and stop zero preparation profiling from the command line. Because some applications use this same signal, you may want to disable the

Node agent 195