DC Activemq not connecting on correct port for HTTPS

Products

• CA Performance Management

Issue/Introduction

 

Installing the DC in Lab environment, and though it appears the installation succeeds, dcmd dies shortly after the installation completes, apparently without making any contact with the DA.  It never shows up in the Data Collectors view, nor via rest/dcms.
I did a tcpdump on both the DC and DA hosts during the installation, and never saw any attempt to communicate between the two.  
The DA is SSL-enabled, and we are also running in an IPv6 environment. Ports are accessible through the firewall.  SE Linux is disabled.
During the installation I entered the IPv6 addresses of both the primary and secondary DAs.

activemq.log.shows it trying to connect on an incorrect address/port

ERROR | Failed to connect to [tcp://x.x.x.x] after: 3 attempt(s) | org.apache.activemq.transport.failover.FailoverTransport | ActiveMQ Task-1

 

$ grep x.x.x.x/etc/hosts
x.x.x.x        DA01.dev.com DA01

netstat -na | grep 616 | grep -v localhost | grep LISTEN
tcp6       0      0 :::61616                :::*                    LISTEN
tcp6       0      0 :::61617                :::*                    LISTEN
tcp6       0      0 :::61618                :::*                    LISTEN
tcp6       0      0 :::61619                :::*                    LISTEN
tcp6       0      0 :::61620                :::*                    LISTEN
tcp6       0      0 :::61621                :::*                    LISTEN
tcp6       0      0 :::61622                :::*                    LISTEN
tcp6       0      0 :::61623                :::*                    LISTEN

 

grep networkConnector /opt/IMDataCollector/broker/apache-activemq-5.16.2/conf/activemq.xml

   <networkConnectors>
                    <networkConnector name="da_manager" uri="static:(failover:(tcp://x.x.x.x,tcp://x.x.x.x)?maxReconnectAttempts=3)" duplex="true"

Environment

Release : 21.2

Component :

Cause

It appears that install code isn't reading the IPv6 address correctly and thinks the 2nd hex value is a port; then adds it at the end. 

 the first install was done using the IPv6 addresses for the primary and secondary DAs in the install dialog

Resolution

1 Uninstall the DC

2. Reinstall the DC using FQDN for the DAs, in the install dialog, which will now reflect the correct port in (61616) /opt/IMDataCollector/broker/apache-activemq-5.16.2/conf/activemq.xml

 

     $ grep networkConnector /opt/IMDataCollector/broker/apache-activemq-5.16.2/conf/activemq.xml
             <networkConnectors>
                         <networkConnector duplex="true" name="da_manager" suppressDuplicateTopicSubscriptions="false" uri="static:(failover:(tcp://DA01:61616,tcp://DA02:61616)?