Execution Server Unreachable

book

Article ID: 37733

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Problem: 

An execution server is showing as unreachable after configuring it to use SSL per the instructions given here: https://docops.ca.com/ca-release-automation/5-5-2/en/installation/ca-release-automation-communications-security/secure-communications#SecureCommunications-SecureManagementServertoExecutionServerCommunication

 

Environment:  

CA Release Automation 5.5.2

CA Release Automation Execution Server on Linux

 

Cause: 

A typo was made while specifying the jms.key.store property inside of the webapps/execution/WEB-INF/jms.properties file. If this is the cause for your execution server becoming unreachable then it can be confirmed by checking execution server logs - around the time of startup. For this cause, as there may be others, you will specifically find messages inside of the nolio_exec_all.log with the text:

Invocation of init method failed; nested exception is java.lang.RuntimeException: java.io.FileNotFoundException: class path resource [conf/custom-keyStore.jks] cannot be opened because it does not exist;

Going back over the instructions to configure the Execution Server to use SSL (in the URL above) we see that conf/customkeystore.jks is specified in two files:

  1. webapps/execution/WEB-INF/jms.properties
  2. conf/server.xml

In this case the webapps/execution/WEB-INF/jms.properties file was updated to use: jms.key.store=conf/custom-keyStore.jks (notice the upper case S in keyStore).  

 

Resolution:

Confirm the cause described above applies to your situation. If so then update the webapps/execution/WEB-INF/jms.properties file to specify the correct file name for the jms.key.store (case sensitive on Linux). Then recycle the Execution Server service. 

Environment

Release:
Component: RAEXS