How to Resolve the Network Connection DA Issue
search cancel

How to Resolve the Network Connection DA Issue

book

Article ID: 10299

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

Message errors PC DMService.log file

ERROR | pool-4-thread-3 | AAAA-MM-DD HH:MM:SS,958 | com.ca.im.portal.api.services.datasource.DataSourcePoll 

| Received WebServiceException from version check for data source Data Aggregator@HOST. CAUSE=org.apache.cxf.transport.http.HTTPException: HTTP response '404: Not Found' when communicating with http://DA:8581/DataSourceWS. MESSAGE=Could not send Message.. Returning DS_COMM_FAILURE result. 

OR

ERROR | pool-4-thread-3 | AAAA-MM-DD HH:MM:SS,959 | com.ca.im.portal.dm.productsync.DataSourcePoller 

| Unable to contact data source Data Aggregator@DA

 



Environment

Release:PM all release 

Resolution

Pay attention: If you are using DA on Fault Tolerance don't use this article

Here is the procedure to resolve the connection issue between DA and Dr or the synchronization issue

1. Stop activemq and the dadaemon on DA.

/opt/IMDataAggregator/scripts/activemq stop

/opt/IMDataAggregator/scripts/dadaemon stop 

2. Move the data directory the data directory. 

mv/opt/IMDataAggregator/apache-karaf/data /opt/IMDataAggregator/apache-karaf/data_OLD

3. Move the kahadb file. 

mv /opt/IMDataAggregator/data/broker/kahadb /opt/IMDataAggregator/data/broker/kahadb_OLD

4. Move the local-jms-broker.xml file 

mv /opt/IMDataAggregator/apache-karaf/deploy/local-jms-broker.xml /opt/IMDataAggregator/apache-karaf/deploy/local-jms-broker.xml_OLD

5. Start the DA (note the dadaemon start will start the activemq process also)

/opt/IMDataAggregator/scripts/dadaemon start