Process Automation - Agent is not starting up

book

Article ID: 197090

calendar_today

Updated On:

Products

CA Process Automation Base Process Automation Manager

Issue/Introduction

PAM Agent service is started, but after few minutes it stops by itself.

c2o.log doesn't show any specific error that may help to understand the issue.

Cause

In order to obtain more information of the problem, first thing to do is to increase log level to DEBUG instead of INFO, which is explained here:

Increase logging levels for ITPAM Agent logs

Additionally to this, in order to get more logging information, the c2oagtsvcw.conf file can be edited (in the root of /pamagent/) with the following:

Set wrapper.logfile.loglevel=DEBUG

After this was done and reprocuding the issue, the following can be seen on c2ow.log :

INFO   | jvm 1    | 2020/08/10 18:46:44 | Activate jar: file:/C:/Program Files/CA/PAM Agent/PAMAgent/.c2orepository/.c2oagentresources/lib/jetty/jars/slf4j-api-1.6.1.jar
INFO   | jvm 1    | 2020/08/10 18:46:44 | Activate jar: file:/C:/Program Files/CA/PAM Agent/PAMAgent/.c2orepository/SystemRepositoryData.xml
INFO   | jvm 1    | 2020/08/10 18:46:44 | Exception in thread "CA Agent Startup" java.lang.UnsupportedClassVersionError: org/mozilla/javascript/ScriptableObject : Unsupported major.minor version 52.0

INFO   | jvm 1    | 2020/08/10 18:46:44 | WrapperSimpleApp: main method completed
INFO   | jvm 1    | 2020/08/10 18:46:44 | Wrapper Manager: ShutdownHook started
INFO   | jvm 1    | 2020/08/10 18:46:44 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook

DEBUG  | wrapperp | 2020/08/10 18:46:44 | read a packet STOP : 0
DEBUG  | wrapper  | 2020/08/10 18:46:44 | JVM requested a shutdown. (0)

Environment

Process Automation:

Orchestrator on 4.3 SP05 (Java 1.8)

Agent on 4.3 SP02 (Java 1.7)

Resolution

Error related to "minor/major" versions are related to the Java release the Agent currently have, but on this scenario there is more.

The Orchestrator on release 4.3 SP05 has a new Tanuki Wrapper release, technically any Agent with SP04 and older will be able to still communicate with this Orchestrator while they are running, once they stop (abend or not) it's expected that they won't be able to communicate back again since it tries to get the updated wrapper info from the Orchestrator, but is not compatible with current Java 7 installed on the AGent, but not only this, SP05 Agents are completely different (from code perspective).

The best way to solve this is to upgrade Java to 1.8 and also move the Agent version to the same level than Orchestrator

Additional Information

Working with Agents that have an older release (and also old Java release) than the Orchestrator is not supported and definitely not recommended.