Could not refresh JMS Connection for destination 'ac_server_to_server_broadcast'
search cancel

Could not refresh JMS Connection for destination 'ac_server_to_server_broadcast'


Article ID: 133612


Updated On:


CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager (PAM)


On Red Hat Enterprise Linux, ActiveMQ is not starting with the following in wrapper.log.

Could not refresh JMS Connection for destination 'ac_server_to_server_broadcast' - retrying using FixedBackOff{interval=5000, currentAttempts=2, maxAttempts=unlimited}. Cause: Could not create Transport. Reason: Broker named '<HOST or FQDN>' does not exist.


PIM 14 and above.


ActiveMQ is running under openjdk instead of the oracle jdk installed with the 3rd party components.

You can check if this is the case by executing:

ps aux | grep

If openjdk is the cause, this will return something like:

root 5175 14.7 2.5 7951868 313736 ? Sl 11:03 0:11 /usr/lib/jvm/java-1.8.0-openjdk- -Dactivemq.home=.. ... etc etc ...


Need to make sure that it uses the same java VM as other PIM components - the java vm installed with the 3rd party components. 

The suggested way to achieve this is documented in the manual:

Pay particular attention to step 7.d.ii:

'Append the JDK/bin path to the system PATH. 

For example, to set the path "/usr/java/jdk1.8.0_101/" using the bash shell, enter the following command:

# export PATH=/usr/java/jdk1.8.0_101/bin:$PATH

However, this will make oracle java the default for the entire system. If you just want to set oracle jdk for ActiveMQ (as is done for other PIM components) you can set in wrapper.conf.