HP

HPjmeter 4.1 User's Guide

English
  HPjmeter 4.1 User's Guide > Chapter 10 Troubleshooting   

Console

  • If a node agent is not running, the console cannot connect to JVM agents and you will get this message in the console status bar when you try to attach to a managed node:

    Connection to hostname failed.

    You can set up the node agent to run as a daemon or service for automatic, continuous operation, or as a normal process when you do not need continuous operation. The setup process depends on your platform.

  • The console graphical interface uses the HP One Voice look and feel for presentation. When you run the console remotely, performance with this look and feel can be sluggish. Use the standard Java Metal look and feel when displaying the console remotely.

  • The console may occasionally report an incorrect application name.

  • As expected for any Java application during long-running or intensive monitoring sessions, the console may run out of memory. In this case, the console will not terminate; instead, it stops reporting data, closes the active session if possible, and reports an OutOfMemoryError. A message appears in the controlling terminal and on the main window's status bar. This can also occur if you try to open a data file that is larger than the memory allowed for the console.

    Try restarting the console with the -Xmx option set to a larger value. The default for -Xmx is 256 MB. Please see the next section on JVM agent troubleshooting to see how the JVM agent behaves under this condition.

  • On occasion, you can successfully connect to the JVM and open a session, but discover that no metrics are available for viewing (menu options are grayed out). This can occur if the application is experiencing a long GC at the time that you open the session.

    Once the GC completes, the console should begin receiving data and behave normally.

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

    $ JMETER_HOME/bin/hpjmeter -log level_of_detail

    Available log levels:

    • FINEST (most impact on performance)

    • FINER

    • FINE

    • CONFIG

    • INFO

    • WARNING (default setting)

    • SEVERE (least impact on performance)

    • OFF (turn off logging)