IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
data collector fails to start
The following content provides solutions when the Data Collector fails to start.
data collector fails to start on WebLogic 8 cluster
The problem: After the data collector is successfully installed and configured on the WebLogic 8 cluster, both WebLogic and the data collector cannot be restarted.
The solution: This happens when WebLogic server instance is started by different JDKs. For example, the first time it might be started with BEA JDK and the second time SUN JDK. Because the data collector configuration is JDK specific, reconfigure the data collector to collect the correct JDK vendor information after you change the JDK.
Tomcat data collector does not start after installation and configuration
The problem: After the Tomcat data collector is installed and configured, the data collector does not start.
The solution: The problem is the result of the limited page size of AIX. Sometimes after a data collector is installed on AIX, the data collector issues an Out of Memory (OOM) error and stops. In this case, determine whether the AIX page size is large enough. If it is not, set the AIX system environment with the following shell command:
export LDR_CNTRL=MAXDATA=0x30000000The value of 0x30000000 is provided as an example only. You must determine the correct value to set based on your environment.
Before you install the Tomcat data collector, determine whether the IBM 64-bit JDK 1.4 has data size limitations that might cause an Out of Memory error while a large application is processed. If it has data size limitations, run the following command:
ulimit -d unlimited
WebSphere Community Edition data collector startup fails
The problem: After installing the data collector, WebSphere Community Edition cannot startup.
The solution: Search in <SERVER_HOME>/var/log/geronimo.out (on Linux) or console printout (on Windows) and see if there is a Port already in use: <port> exception. This exception means that another program (for example another WebSphere Community Edition instance) has occupied that port.
Either shutdown the other program to release the port or modify <SERVER_HOME>/var/config/config.xml and set another port number.
When the shutdown.sh command finishes executing on Linux, there is a delay (approximately 15 seconds) before the process is fully shut down. Use the command ps ef | grep java to make sure the process is fully shut down before restarting the server.
Parent topic:
data collector