"Could Not Create the Java Virtual Machine" when trying to start CA Access Gateway (SPS) after upgrading to AdoptOpenJDK 11/17
Article ID: 264451
Updated On:
Products
Issue/Introduction
After upgrading the JDK used by CA Access Gateway (SPS) from JDK 8 to JDK 11 (AdoptOpenJDK), the appropriate update was made to the SmSpsProxyEngine.properties file; however, the embedded Tomcat server does not start properly when the Access Gateway services are started.
On the Windows version, Windows services show that the Access Gateway services have started.
The Event Viewer has no warnings or errors that point to the cause.
On Linux version, there's no log files created except nohup.log, which shows the following entry:
-Djava.endorsed.dirs=/{home_SPS}/Tomcat/endorsed is not supported. Endorsed standards and standalone APIs in modular form will be supported via the concept of upgradeable modules.
Error: Could not create the Java Virtual Machine.Error: A fatal exception has occurred. Program will exit.
Environment
CA Access Gateway (SPS) 12.8.x, 12.9 on Windows or Linux
Cause
The CA Access Gateway (SPS) installation is configured for JDK 1.8. JDK 11 and JDK 17 no longer support the java.endorsed.dirs mechanism (endorsed standards override), so when the JVM is launched with this option pointing to JDK 11/17, it fails immediately — preventing the Access Gateway services (Tomcat component) from starting.
Resolution
There are two available workarounds:
- Reinstall CA Access Gateway (SPS) and let it point to the new JDK
Reinstalling CA Access Gateway (SPS) and pointing the installer to JDK 11 or JDK 17 generates a new SmSpsProxyEngine.properties file on Windows and a new proxyserver.sh file on Linux, both without the obsolete endorsed-directory references. - Manually modify the CA Access Gateway (SPS) modify the environment variable and configuration file as described in documentation (1).
Additional Information
Feedback
