CIC is not starting after upgrading Tomcat

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

After following the steps to upgrade Tomcat explained here:

how to upgrade Tomcat 8.5.56 to 9.0.55 for Web Admin Console (WAC) and Content Import Client (CIC) ?

CIC is not starting up.

When looking at Tomcat logs, the following errors can be seen:

INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files (x86)\CA\SC\CIC\Tomcat
INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files (x86)\CA\SC\CIC\Tomcat
INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files (x86)\CA\SC\CIC\Tomcat\temp
WARNING [main] org.apache.catalina.core.AprLifecycleListener.init The Apache Tomcat Native library failed to load. The error reported was [C:\Program Files (x86)\CA\SC\CIC\Tomcat\bin\tcnative-1.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform]
 java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\CA\SC\CIC\Tomcat\bin\tcnative-1.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform

INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: contextInitialized()
INFO [main] org.apache.catalina.core.ApplicationContext.log SessionListener: contextInitialized()
INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: attributeAdded('StockTicker', 'async.Stockticker@7859fc7')
INFO [Thread-3] org.apache.catalina.core.ApplicationContext.log SessionListener: contextDestroyed()
INFO [Thread-3] org.apache.catalina.core.ApplicationContext.log ContextListener: contextDestroyed()
SEVERE [main] org.apache.catalina.core.StandardContext.loadOnStartup Servlet [action] in web application [/CICManager] threw load() exception
 java.lang.ClassNotFoundException: sun.misc.BASE64Decoder

Environment

Client Automation 14.x

Resolution

These errors may imply a problem with the JAVA used.

On this case, the error is by caused a not properly set variable JRE_HOME, causing that catalina.bat will use the JAVA_HOME instead, which on this particular environment was pointing to another JRE.

JAVA_HOME=C:\Program Files\Eclipse Adoptium\jre-18.0.1.10-hotspot\

In order to solve this problem, the variable JRE_HOME has to point to the JRE included on Client Automation:

JRE_HOME=C:\Program Files (x86)\CA\SC\CIC\jre\

Additional Information

Looking at catalina.bat file, the following instructions can be read:

rem       JRE_HOME        Must point at your Java Runtime installation.
rem       Defaults to JAVA_HOME if empty. If JRE_HOME and JAVA_HOME
rem       are both set,JRE_HOME is used.