IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
The Tivoli Enterprise Monitoring Agent JMX connection socket binding is reported incorrectly
The problem: In some circumstances, the status of the Tivoli Enterprise Monitoring Agent JMX connection socket binding is reported incorrectly.
The reason: By default, the Tivoli Enterprise Monitoring Agent listens to the incoming data collector connections on port 63335, which you can customize during configuration. If the Tivoli Enterprise Monitoring Agent fails to receive incoming connections from the data collector, check whether the Tivoli Enterprise Monitoring Agent socket interface was properly configured and initialized. The possible reason is that another application is listening to the same port as the Tivoli Enterprise Monitoring Agent does. This can lead to lose connection requests from the data collector.
The solution: To resolve this problem, perform the following steps:
- Check the Tivoli Enterprise Monitoring Agent message log or the agent Event workspace in Tivoli Enterprise Portal for the status of socket server initialization. The Tivoli Enterprise Monitoring Agent issues message KYNA0009 or KWJ0027A when socket interface initialization is successful.
On the Windows platform, message KWJ0027A might not be issued when another application is listening on the same port. Use system utilities (such as Netstat) to determine whether a socket conflict has occurred.
- Re-configure your Tivoli Enterprise Monitoring Agent listening port. For information about how to re-configure ITCAM for Application Diagnostics Agent listening port, refer to ITCAM Agent for WebSphere Applications Installation Guides or IBM Tivoli Composite Application Manager: Agent for J2EE Monitoring Agent Installation Guide.
Parent topic:
Troubleshooting: Tivoli Enterprise Portal