Monitoring Framework Issues

C components have slow monitoring performance on Linux (6332884)

Components that rely on C libraries to interface with the Monitoring Framework may display more slowly in the Monitoring Console when they run in the Linux operating environment.

Solution None.

C components do not communicate securely with the node agent (6405037)

Inter-process communication between components that rely on C libraries and the node agent on the same host is not secure. By default, communication uses the loopback interface, thereby reducing the security risk.

Solution None.

Java component have slow SNMP performance (6437945)

Components that rely on Java libraries to interface with the Monitoring Framework may experience performance issues when accessed through SNMP.

Solution None.

Node agent cannot discover monitored components on Solaris 9 (6504230)

Due to a bug in Solaris 9, packets addressed to an IPv4 address are not delivered to listener on an IPv6 socket. This interrupts the discovery mechanism between node agents and the components to be monitored on that host.

Solution Force the node agent's JVM to listen on IPv4 sockets with the following commands:

cacaoadm stop

oldvalue=`cacaoadm get-param java-flags --value`

cacaoadm set-param java-flags="${oldvalue} -Djava.net.preferIPv4Stack=true"

Then restart the node agent, the master agent, and the Monitoring Console with the procedure To Restart a Node Agent in Sun Java Enterprise System 5 Update 1 Monitoring Guide.

Unsynchronized clocks prevent adding a host to the Monitoring Console (6487357)

If the time on the node agent and master agent hosts is too far out of sync, adding that node in the Monitoring Console will fail. The error log of the master agent's Monitoring Framework will report a severe error “during JRMP connection establishment.”

Solution Set the time on either host so they are synchronous.

HP_UX: excessive concurrent monitoring rules causes exception (6481758)

When many monitoring rules are created in parallel in a node agent on the HP-UX operating system, thread numbers in the Java Virtual Machine (JVM) may exceed kernel parameter limits and cause an OutOfMemory exception.

Solution Download and run the HPjconfig tool, as described in the procedure To Optimize Kernel Parameters for Monitoring Framework on HP-UX in Sun Java Enterprise System 5 Update 1 Monitoring Guide.

On Windows mfwkadm generates an error (6535233)

When you run the mfwkadm command on Windows, the following error is generated:

'C:\Program' is not recognized as an internal or external command,

operable program or batch file.

Solution Comment out the fourth line of the file C:\Program Files\Sun\JavaES5\share\mfwk\bin\masetup.bat by adding REM at the start of the line.

if defined MFWK_PATH goto perl_cmd

REM if defined MFWK_PATH goto perl_cmd

Less Severe Monitoring Framework Issues

The following list tracks other known issues with the Monitoring Framework.

6356355

On Linux, discovery does not work when IPv6 is enabled