test

Sun Java Enterprise System 5 Update 1 Monitoring Guide

Troubleshooting the Monitoring Framework

See also the known issues listed in the Sun Java Enterprise System 5 Update 1 Release Notes.

Using the Monitoring Framework on HP-UX Platforms

The kernel parameters on HP-UX are not tuned by default for the task-intensive processing needed by Monitoring Framework running in the Java Virtual Machine (JVM), and this may lead to OutOfMemory exceptions. The following link explains HP-UX kernel settings that affect the JVM: http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,1616,00.html

To configure the HP-UX kernel, download and run the HPjconfig tool as described in the following procedure:

ProcedureTo Optimize Kernel Parameters for Monitoring Framework on HP-UX

  1. Download the HPjconfig tool from the following link and untar the file:

    http://www.hp.com/products1/unix/java/java2/hpjconfig/index.html

  2. Export the display with the following command:


    $ export DISPLAY=IP_address:0.0

  3. Run the HPjconfig tool with the following command:


    Java-binaries/java -jar HPconfig.jar

  4. In the tool's user interface, select the Tunable tab to display the list of current and recommended kernel parameter values. Review the values and click Commit to make the changes. The tool will prompt you to reboot if necessary.

Using the Monitoring Framework on Microsoft Windows

Monitoring Java ES components on the Windows platform through the Monitoring Framework is fully supported, although there are some differences. For example, you must upgrade to Java 1.5 or later to avoid certain known issues. For other known issues, see the Sun Java Enterprise System 5 Update 1 Release Notes.

ProcedureTo Restart a Node Agent

If you need to restart the Common Agent Container that hosts a node agent, the components monitored through that node agent will not accurately reflected in the Monitoring Console until you perform this procedure:

  1. Restart the Common Agent Container that hosts the node agent:


    cacaoadm restart

  2. Restart the Common Agent Container that hosts the master agent. The master agent runs in the Monitoring Framework on the host or in the zone where you installed theMonitoring Console.


    cacaoadm restart

    The master agent will automatically reconnect with all node agents that it was previously monitoring.

  3. Restart the web server that hosts the Monitoring Console:


    /usr/sbin/smcwebserver restart