search cancel

Facing issues with enabling SSL for JMX ActiveMQ in Performance Management DAs and DCs


Article ID: 252548


Updated On:


DX NetOps


I am following the steps detailed here: Configure the Data Aggregator to Use HTTPS Using the SSL Configuration Tool ( to enable SSL for JMX on the Data Aggregator and Data Collectors. I am having some issues - primarily that running <install_path>/scripts/ restarts the activemq and dadaemon processes as part of execution, but the dadaemon process dies shortly after while activemq stays alive. I re-ran the script to disable SSL for JMX and tried starting it again but same issue - if activemq is active, dadaemon dies shortly after.

<install_path>/apache-karaf-4.3.3/data/karaf.out has the following:

OpenJDK 64-Bit Server VM warning: Ignoring option UnsyncloadClass; support was removed in 11.0OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.Exception in thread "JMX Connector Thread [service:jmx:rmi://]" java.lang.RuntimeException: Could not start JMX connector server        at$init$0(        at java.base/ Source)Caused by: The server has been stopped.        at Source)        at$init$0(        ... 1 more



Any help in 


Release : 22.2.1


In DE544549, we found that when we did changes for 22.2.1 for preserving the keystore/truststore filenames, it broke setting up new installs.


The reason dadaemon didn't start up was caused by: [Vertica][VJDBC](100176) Failed to connect to host IVAPP1388096.NYP-LAB.MS.COM on port 5433. Reason: Failed to establish a connection to the primary server or any backup address.ERROR | ExtenderThread-1 | 2022-10-19T15:28:18,703 | shutdown | ces.shutdown.ShutdownManagerImpl 131 | | | Shutting down the data aggregator. The data aggregator can not be started until at least one data repository node is available.It was detected that no data repository nodes were contactable. The uncontactable hosts are:[IVAPP1388096.NYP-LAB.MS.COM]


1. Find this line in IMDataAggregator/scripts/

  cat $DA_HOME/apache-karaf-${KARAF_VER}/etc/jetty-https.xml | sed -e "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/${HTTPS_PORT}/g" > $DA_HOME/apache-karaf-${KARAF_VER}/etc/jetty.xml

  and replace with:

  cat $DA_HOME/apache-karaf-${KARAF_VER}/etc/jetty-https.xml | sed -e "s/@[email protected]/keystore/g" -e "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/truststore/g" -e     "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/${HTTPS_PORT}/g" > $DA_HOME/apache-karaf-${KARAF_VER}/etc/jetty.xml


2. Same issue in DC, replace:

  cat $DC_HOME/apache-karaf/etc/jetty-https.xml | sed -e "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/${HTTPS_PORT}/g" > $DC_HOME/apache-karaf/etc/jetty.xml
  cat $DC_HOME/apache-karaf-${KARAF_VER}/etc/jetty-https.xml | sed -e "s/@[email protected]/keystore/g" -e "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/truststore/g" -e   "s/@[email protected]/${STORE_PASS}/g" -e "s/@[email protected]/${HTTPS_PORT}/g" > $DC_HOME/apache-karaf-${KARAF_VER}/etc/jetty.xml


3. Run to configure HTTPS/JMX SSL correctly