Windows could not start ITPAM service
Article ID: 250899
Updated On:
Products
Issue/Introduction
unable to start CA PAM service getting error message, as process terminated unexpectedly
in the c20w.log file, these messages are recorded
ERROR | wrapper | 2022/09/26 11:23:08 | JVM exited while loading the application.
FATAL | wrapper | 2022/09/26 11:23:08 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2022/09/26 11:23:08 | There may be a configuration problem: please check the logs.
ERROR | wrapper | 2022/09/26 11:24:37 | JVM exited while loading the application.
ERROR | wrapper | 2022/09/26 11:24:42 | JVM exited while loading the application.
ERROR | wrapper | 2022/09/26 11:24:47 | JVM exited while loading the application.
ERROR | wrapper | 2022/09/26 11:24:52 | JVM exited while loading the application.
ERROR | wrapper | 2022/09/26 11:24:56 | JVM exited while loading the application.
FATAL | wrapper | 2022/09/26 11:24:57 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2022/09/26 11:24:57 | There may be a configuration problem: please check the logs.
Environment
Release : 4.3
Component : Process Automation
Resolution
Check the c2osvcw.conf file for parameter wrapper.java.command. For example
wrapper.java.command=C:/Program Files/Java/jdk1.8.0_191/bin/java
now go to command prompt, and run
C:\Program Files\Java\jdk1.8.0_191\bin\java -version
if it returns error regarding the VM, then the jdk is corrupt and this is the reason why PAM does not start
Fix this jdk issue(for example, download the same version of jdk from Oracle web site and replace the existing jdk, after backup) and PAM should start fine.
Additional Information
1.- If you are having issue while restarting PAM, be sure first that no Java.exe remain running. If you have any, check if that instance of Java is tied to the Orchestrator or not, but if you see is not tied to any critical app installed on your server, kill it from Task Manager and then try to start PAM service.
2.- Another good verification is to check what is actually failing during startup. Once you start PAM service, you will see in Task Manager a Java.exe instantiated, which will start consuming around 1 GB to 2 GBs, after a while, a second Java.exe will be instantiated, which will consume around 300 MB. The idea here is to check if this whole situation happens, if the first Java.exe starts but then fails, it means a problem with the PAM engine is being present, but if the second Java.exe starts, and then it fails, while the first one is still running (but eventually will also fail), it means the module affected is ActiveMQ, which gives you access to PAM's UI.
3.- Additionally to the above, sometimes when PAM has been running for several weeks it's recommended to perform a simple cleanup before trying to start it. The steps to do this are:
- Stop Orchestrator service.
- Navigate to '..PAM\server\c2o' and delete (or cut and paste them on the desktop, outside of CA folder) the following folders:
data
logs
scripts
tmp
temp
work
wrappers
- Start Orchestrator service
Most of the common problems that a PAM server is using can be solved this way.
4.- Also suggest to verify the amount of memory allocated for your Orchestrator, there is no magic numbers here, but since PAM consumes a lot of memory during its normal execution, suggest to set at least 8 GBs (which means your server requires at least 12 GB of total memory). The steps to configure this are explained in KB Article 32448.
Feedback
