Data Aggregator (DA) fails to connect or synchronize with CA Performance Manager (CAPM)
search cancel

Data Aggregator (DA) fails to connect or synchronize with CA Performance Manager (CAPM)


Article ID: 6704


Updated On:


CA Infrastructure Management CA Performance Management - Usage and Administration


A Data Aggregator and a Data Collector were both installed on the same system in a pre-production environment. The Data Collector was uninstalled to prepare to install it on a separate server from the Data Aggregator. After taking this step the Data Aggregator no longer connects or synchronizes with the CA Performance Manger server.


All supported releases


Both the Data Aggregator and Data Collector installations rely on ActiveMQ code and services to communicate with other systems in the CA Performance Manager product environment.

Both have files and paths in common but aren't designed to be installed on the same server.

When one of the products is uninstalled, it removes the ActiveMQ software installed along with the CA software.

This causes ActiveMQ files necessary to successful function to be removed preventing the remaining tool from correct operation.


The solution to this problem is as follows:

  1. Re-run the DA install to reset the activemq files. Follow the standard Wiki Doc user guide instructions for an upgrade to re-run the installDA.bin and reinstall it on top of what is left.
  2. Restart the dadaemon


Additional Information

Tips for Success:

  • Verify that the /etc/init.d/activemq file has the dahome= and activemqhome= home path variables set correctly.
  • If the /opt/IMDataAggregator/broker/apache*/conf/activemq.xml file is missing the DA karaf.log file will contain errors due to an inability to establish a connection to activemq. The activemq.log file will show errors regarding inability to find activemq.xml file. In this event, if available we can copy the activemq.xml file from a matching system at the customer site or from a CA support lab over to the problem server. Ensure permissions are correct (775 and root:<Group>) and it should see the new file and begin to work properly.
  • Still seeking connection issues? Try running this on the problem host as the install owner (normally root) "chkconfig --list activemq". If nothing is returned, to resolve it run the following "chkconfig --add activemq".