IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Tivoli Enterprise Monitoring Agent fails to work

You might have met the situation that Tivoli Enterprise Monitoring Agent fails to work. The following content provides some solutions to this situation.


Tivoli Enterprise Monitoring Agent stops because of lack of memory

The problem: The Tivoli Enterprise Monitoring Agent reports the following errors:

The reason: These error messages indicate that the Tivoli Enterprise Monitoring Agent is experiencing a high load and lack of available memory.

The workaround: To resolve this problem, take one of the following actions:

Refer to http://www.ibm.com/developerworks/java/jdk/diagnosis for more information about Java troubleshooting tips.


Tivoli Enterprise Monitoring Agent fails to start or recycle the WebSphere Application server

The problem: The Tivoli Enterprise Monitoring Agent fails to start or recycle the WebSphere Application server when running a memory-intensive Java application in a 32-bit Java virtual machine (JVM). The error message JVMST018 shown below will appear in the native_stderr.log file.

# ./java -version -Xms128M -Xmx2048M
[ **Out of memory, aborting** ]                   
[  ]                                              
[ *** panic: JVMST018: Cannot allocate memory for 
initializeMarkAndAllocBits(allocbits1) ]           

The reason: This problem occurs because the maximum Java heap size for the WebSphere Application server is set to a value that is too large.

The workaround: Lower the maximum heap size.


Tivoli Enterprise Monitoring Agent failed to work after re-configuration

The problem: After re-configuring, Tivoli Enterprise Monitoring Agent failed to work.

The cause: The configurator tool picked up the Java Runtime Environment (JRE) 1.6 that was set as the default system JRE in the JAVA_HOME environment variable. Tivoli Enterprise Monitoring Agent requires JRE 1.4.x, by default located in C:\Program Files\IBM\Java142.

The solution: Set your JAVA_HOME system environment variable to point to the JRE that was installed by IBM Tivoli Monitoring (on Tivoli Enterprise Portal Server) or the JRE installed by the base product driver then re-configure the monitoring agent.


Parent topic:

All platforms

+

Search Tips   |   Advanced Search