Debugging

Follow the following steps to debug Connection Manager:

  1. Make sure that you configure the Connection Manager CMA, CMS, and Internet Server nodes with the correct connectivity information and password. On the Add Connection Manager Node page, click the Test button to verify that the connectivity information is correct.
  2. Verify that the firewall ports are opened as defined in the Firewall Considerations.
  3. Use TIBCO MFT Command Center to configure Internet Server, CMA, and CMS. If you cannot use to retrieve configuration, a message is displayed to show the error. If you receive a connection error, check the following things:
    • Verify that the firewall has been opened for the necessary ports.
    • Verify that the IP address and IP port have been configured correctly.
    • Issue a NETSTAT command on the Connection Manager node to make sure the Connection Manager node is listening on the defined port.
  4. If you have connectivity to the Connection Manager nodes, but connections fail, use the CMA Get Status > Test function. This function tests whether CMA can access the defined internal server. TIBCO MFT Command Center tests are initiated from the CMA TCP Loopback address (127.0.0.1); therefore, make sure that the CMA Accept Connections from These Internet Servers field is configured to accept changes from 127.0.0.1 and ::1, in addition to the IP addresses of the Internet Server computers. Otherwise, tests initiated from TIBCO MFT Command Center fail with an error indicating that CMA will not accept requests from local host.
  5. Tracing can be configured to assist in debugging. For CMA and CMS, the default tracing is INFO; for Internet Server, the default tracing is ERROR. This writes trace files to the following directories:
    • CMA: <CMA_Install>/bin/RPLog.txt
    • CMS: <CMS_Install>/bin/RPLog.txt
    • Internet Server: <MFTIS_Install>/server/logs/catalina.out

    Generally speaking, look at the CMS tracing first. The CMS tracing documents problems in connecting to CMA.