Upgrade of a 11.4 SP3 WCC server with no known errors in the install log results in the CA-wcc-service not staying started.

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• CA Workload Automation Agent

Issue/Introduction

Introduction: 

Upgrade of a 11.4 SP3 WCC server with no known errors in the install log results in the 

CA-wcc-service not staying started.

 

Question: 

Just upgraded from 11.3.6 to 11.4 SP3.  The CA-wcc service keeps shutting down with tomcat errors:

 

Mar XX, 2016 1:49:59 PM org.apache.catalina.core.ContainerBase startInternal

INFO   | jvm 1    | 2016/03/17 13:49:59 |      156 | SEVERE: A child container failed during start

INFO   | jvm 1    | 2016/03/17 13:49:59 |      156 | java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]

 

and

 

SEVERE: A child container failed during start

INFO | jvm 1 | 2016/03/17 12:08:13 | 137 | java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/wcc/doc]]

 

Caused by: java.lang.IllegalArgumentException: The main resource set specified [/opt/CA/WorkloadCC/tomcat/webapps/../../doc] is not valid

 

Environment:  

WCC 11.4 SP3 Linux,Unix

 

Answer: 

Check to see if /opt/CA/WorkloadCC/tomcat/webapps/../../doc exists or permission are set correctly. It should match the other directories located in the directory.

 

Environment

Release: ATSYHA99000-11.4-Workload Automation AE-High Availability Option
Component: