Troubleshoot Application Topology Composer (ATC)

Why does the connectivity test return "isConnected false"?

The test engine uses Telnet to check whether the destination port is reachable. If the port is unreachable, the test engine returns the following message:

telnet XX isConnected false, please check the instance isReachable, execute ping [ip] or telnet [ip] [port]

Cause: The target application is not listening on the expected port. Because the request never reaches the destination node, trace data for the connection is also empty.

Solution: Verify that the target application is running and listening on the correct port. Run the following command to test connectivity:

telnet <target-ip> <target-port>

If the command fails, check the application process status and confirm the port configuration.

Why is the instance list empty?

The test engine discovers instances by reading the service list of an application. A normally registered service list looks like this:

Cause: The application is not registered for services.

Solution: Check whether service registration completed successfully for the application. If no instances appear, the application has not registered its services with the registry. Review the service registration configuration and make sure the application started without registration errors.

Why can't I click a trace to view its details?

Only EDAS applications support clickable traces in ATC.

Workaround for non-EDAS applications: If a non-EDAS service indirectly calls an EDAS application, a trace ID is displayed in the ATC view. Copy the trace ID and query it in the EDAS tracing console to view the trace details.