CA Workload Control Center services fail to start.
The CA WCC log file CA-wcc-services.log has the following error captured.
STATUS | wrapper | 2020/09/16 21:28:19 | 14 | Launching a JVM...
DEBUG | wrapper | 2020/09/16 21:28:19 | 14 | Java Command Line:
DEBUG | wrapper | 2020/09/16 21:28:19 | 14 | Command: "..\..\jre_32\bin\java" -Djava.endorsed.dirs=../common/endorsed -Dcatalina.base=.. -Dcatalina.home=.. -Djava.io.tmpdir=../temp -Djava.awt.headless=true -D"javax.net.ssl.trustStore=E:\Program Files\CA\Workload Control Center/data/config/.keystore" -D"CA_WCC_INSTALL_LOCATION=E:\Program Files\CA\Workload Control Center" -Dhazelcast.logging.type=log4j -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dhazelcast.icmp.enabled=true -XX:+UseConcMarkSweepGC -Dorg.bouncycastle.rsa.allow_multi_use=true -Xms256m -Xmx1500m -Djava.library.path="../lib;../../bin;%ADDL_LIBRARY_PATH%;E:\Program Files\CA\WorkloadAutomationAE\autosys\bin" -classpath "../lib/classes;../lib/access-11.4.7.0-164.jar;../lib/access-resources-11.4.7.0-174.jar;../lib/accessors-smart-1.2.jar;../lib/annotations-api.jar;../lib/apache-mime4j-0.6.jar;../lib/asm-5.0.4.jar;../lib/bc-fips-1.0.1.jar;../lib/catalina-ant.jar;../lib/catalina-ha.jar;../lib/catalina-storeconfig.jar;../lib/catalina-tribes.jar;../lib/catalina.jar;../lib/commons-codec-1.11.jar;../lib/commons-lang-2.1.jar;../lib/commons-logging-1.2.jar;../lib/commons-logging-api-1.1.1.jar;../lib/db-resources-11.4.7.0-168.jar;../lib/derbyclient-10.12.1.1.jar;../lib/ecj-4.6.3.jar;../lib/eclipselink-2.3.1.jar;../lib/eem-safex-12.6.1.0.jar;../lib/el-api.jar;../lib/flow-model-11.4.7.0-165.jar;../lib/hazelcast-all-3.9.1.jar;../lib/httpclient-4.5.6.jar;../lib/httpcore-4.4.10.jar;../lib/httpcore-nio-4.4.10.jar;../lib/httpmime-4.5.6.jar;../lib/jasper-el.jar;../lib/jasper.jar;../lib/jaspic-api.jar;../lib/jcip-annotations-1.0-1.jar;../lib/jpa-2.0-20091110.060925-5.jar;../lib/json-smart-2.3.jar;../lib/jsp-api.jar;../lib/log4j-1.2.17.jar;../lib/log4j-contrib-1.0.4.jar;../lib/mssql-jdbc-6.2.1.jre7.jar;../lib/nimbus-jose-jwt-5.4.jar;../lib/not-yet-commons-ssl-0.3.10.jar;../lib/ojdbc7-12.1.0.2.0.jar;../lib/security-11.4.7.0-172.jar;../lib/servlet-api.jar;../lib/snakeyaml-1.23.jar;../lib/tomcat-api.jar;../lib/tomcat-coyote.jar;../lib/tomcat-dbcp.jar;../lib/tomcat-i18n-es.jar;../lib/tomcat-i18n-fr.jar;../lib/tomcat-i18n-ja.jar;../lib/tomcat-i18n-ru.jar;../lib/tomcat-jdbc.jar;../lib/tomcat-jni.jar;../lib/tomcat-util-scan.jar;../lib/tomcat-util.jar;../lib/tomcat-websocket.jar;../lib/ujccapi-11.3.6.1643.jar;../lib/websocket-api.jar;../lib/wrapper.jar;../lib/xercesImpl-2.9.1.jar;../lib/xml-apis-1.3.04.jar;../bin/bootstrap.jar;../bin/commons-daemon.jar;../bin/tomcat-juli.jar;E:\Program Files\CA\WorkloadAutomationAE\autosys\bin/asapi.jar;E:\Program Files\CA\WorkloadAutomationAE\autosys\bin/log4j-1.2.16.jar;E:\Program Files\CA\WorkloadAutomationAE\autosys\bin/ujccapi.jar;../conf" -Dwrapper.key="6C9hiy4KgHn-ZvbH-HAF2Wh48ufSXFuO" -Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=9676 -Dwrapper.version="3.5.37-st" -Dwrapper.native_library="wrapper" -Dwrapper.arch="x86" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=4 -Dwrapper.lang.domain="wrapper" -Dwrapper.lang.folder="../lang" org.tanukisoftware.wrapper.WrapperStartStopApp org.apache.catalina.startup.Bootstrap 1 start org.apache.catalina.startup.Bootstrap true 1 stop
DEBUG | wrapper | 2020/09/16 21:28:19 | 14 | JVM started (PID=10456)
INFO | jvm 4 | 2020/09/16 21:28:20 | 14 | Error occurred during initialization of VM
INFO | jvm 4 | 2020/09/16 21:28:20 | 14 | Could not reserve enough space for 1536000KB object heap
DEBUG | wrapper | 2020/09/16 21:28:20 | 14 | JVM process exited with a code of 1, setting the Wrapper exit code to 1.
DEBUG | wrapper | 2020/09/16 21:28:20 | 14 | 1: STATUS_WAIT_1 (0x1)
ERROR | wrapper | 2020/09/16 21:28:20 | 14 | JVM exited while loading the application.
DEBUG | wrapper | 2020/09/16 21:28:20 | 15 | Preparing to restart with mode 2.
DEBUG | wrapper | 2020/09/16 21:28:20 | 15 | JVM was only running for 0 seconds leading to a failed restart count of 4.
DEBUG | wrapper | 2020/09/16 21:28:20 | 15 | Waiting 5 seconds before launching another JVM.
Release : 11.3.6, 11.4 and higher
Component : CA Workload Control Center
The failure is due to the limitation on the max-heap can be set for JRE x32bit applications on x64 platforms.
https://www.oracle.com/java/technologies/hotspotfaq.html#gc_heap_32bit