Troubleshooting the Monitoring Framework

See also the known issues listed in the Sun Java Enterprise System 5 Release Notes for UNIX.

Using the Monitoring Framework on HP-UX Platforms

The Java Virtual Machine (JVM) on HP-UX is not tuned by default for the task-intensive processing needed by Monitoring Framework, and this may lead to OutOfMemory exceptions. To configure the JVM, download and run the HPjconfig tool from the following location:http://h21007.ww2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,1620,00.html.

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 Release Notes for Microsoft Windows.

To 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 be visible 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