test

Sun Java Enterprise System 5 Release Notes for UNIX

Monitoring Framework Issues

Linux IPv6 loopback interface not supported (6356355)

On a Linux system, the Monitoring Framework will not work when IPv6 is enabled. As a result, the instrumentation of your monitored components on this system will not be loaded into the cacao container, and you will not see them in the Monitoring Console.

Solution There are two possible solutions:

Undeploying a monitored component from a node agent can cause a deadlock (6481273)

In the process of disabling a monitored component, it should be undeployed from its node agent, but this sometimes freezes. Specifically, the cacaoadm undeploy command never returns and monitoring is blocked in the entire node agent.

Solution Kill the process and 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 Monitoring Guide.

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 may have slower monitoring performance after node operations (6410218)

Components that rely on C libraries may exhibit slower monitoring performance in the Monitoring Console after other components in the same node agent are redeployed or terminated.

Solution Restart the node's Common Agent Container including the node agent, then restart the master agent and the Monitoring Console with the procedure To Restart a Node Agent in Sun Java Enterprise System 5 Monitoring Guide.

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 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.

Documentation of private C API not supported (6463023)

Documentation for a private C API was inadvertently included in the run-time packages. The interfaces it describes are private and subject to change at any time, therefore their use is discouraged.

Solution None.

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 Monitoring Guide.