Execution Server Not Starting After Applying b576

Products

• CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

After applying b576, we start the service for the execution server but it does not stay running. 

Environment

Release : 6.7

Component : CA RELEASE AUTOMATION EXECUTION SERVER

Cause

Applying cumulative patch b576 replaces the conf/server.xml with a version of the file that uses the default ports. This is a problem on execution servers (NES) that are installed on the same machine as the management server (NAC) - specifically when it is installed to a different directory. The reason this is a problem is because both services (NAC and NES) try to use the same ports. 

 

If this problem is happening then the problem is typically accompanied by the following error message(s) in the <NESInstallDir>/logs/admin.0.log:

SEVERE: Failed to initialize component [Connector[HTTP/1.1-8080]]
org.apache.catalina.LifecycleException: Protocol handler initialization failed
   ....
   ....
Caused by: java.net.BindException: Address already in use

 

Resolution

To solve this problem:

1. Make sure the services for the NES are stopped.
2. Create a backup of the NES's conf/server.xml file. 
3. Update the conf/server.xml configuration file on the NES to use different ports.
4. Start Services.

 

If you are not sure which ports the Execution Server used before applying the b576 cumulative patch, you can review a backup of the file in the folder: <NESInstallDir>/patchBackup/6.7.0.576/conf/server.xml.