IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Managing Server and data collectors require a restart after IP address change
The problem: The Managing Server and data collectors require a restart after a DHCP IP address change. The kernel stops serving the RMI (remote method invocation) codebase correctly to the other components; the data collectors don't try to reconnect to the Publishing Server, even after the Publishing Server has been restarted. Both still reference the old IP address, and they show up as unavailable in the Application Monitor. Nothing crashes , but the kernel RMI socket stops serving the classes correctly.
The first exception on the Managing Server is an IOException Socket Closed event, followed by many socket exceptions.
The solution: Use dynamic DNS, and have the kernel host and RMI codebase parameters set on the data collector using the dynamic DNS name for this Managing Server rather than the IP address; see the IBM Tivoli Composite Application Manager for WebSphere Installation and Customization Guide.
Parent topic:
All platforms
Parent topic:
Run the Managing Server