Agent cannot be started after changing the java to OpenJDK
search cancel

Agent cannot be started after changing the java to OpenJDK

book

Article ID: 205104

calendar_today

Updated On:

Products

CA Workload Automation AE - System Agent (AutoSys) Workload Automation Agent Autosys Workload Automation

Issue/Introduction

After changing the java version used by the agent to OpenJDK,

the agent service can not be started.

 

Environment

Release : 11.4

Component : CA Workload Automation Agent

Resolution

The encountered problem was related to the “oscomponent.libjvmpath” not set to the new java path value.

We could find the following error in the “nohup.stderr” file of the agent:

dlopen: /local/apps/autosyswa/WorkloadAutomationAE/SystemAgent/WA_AGENT/jre/lib/amd64/libjava.so: cannot open shared object file: No such file or directory

Verifying the “agentparm.txt” file the “oscomponent.libjvmpath” is set to:

oscomponent.libjvmpath=/local/apps/autosyswa/WorkloadAutomationAE/SystemAgent/WA_AGENT/jre/lib/amd64/libjava.so

The recommended solution is to update the “oscomponent.libjvmpath” parameter in “agentparm.txt” file to point to the new java path before trying to restart the agent.

Problem resolved by applying the solution.