AutoSys Web Server / Agent / WCC Services Fail to Start After OS Patching

Products

• Autosys Workload Automation

Issue/Introduction

After OS, AutoSys services (specifically the Agent and the Web Server) fail to start.

Log analysis indicates a "No such file or directory" error when the wrapper attempts to locate the Java Runtime Environment (JRE) command.

• Web Server logs contain errors like this:
  WARN   | wrapper  | 2026/08/21 09:22:58 | The configured wrapper.java.command could not be found, attempting to launch anyway: ../../JRE_WA/bin/java
ERROR  | wrapper  | 2026/08/21 09:22:58 | Unable to start JVM: No such file or directory (2)


• Agent logs contain errors like:
  08/21/2026 09:46:56.351-0400: Database check succeeded
08/21/2026 09:46:56.351-0400: JVM doesn't exist at the specified java path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.422.b05-2.el8.x86_64/jre/bin/

Cause

During the patching process, the underlying Java installation path was either updated or removed. Consequently, the hard-coded paths in the agentparm.txt configuration file and the relative symbolic links in the Application directory (JRE_WA and JRE64_WA) point to invalid or non-existent directories.

Resolution

Update the AutoSys Agent Configuration:

• Locate the agentparm.txt file.
• Find the oscomponent.javapath parameter.
• Update the value to point to the current Java location, typically:
  oscomponent.javapath=/etc/alternatives/jre_openjdk
• Save the file and restart the AutoSys Agent.

Update Web Server Symbolic Links:

• The Web Server uses symbolic links (JRE_WA and JRE64_WA) to locate the JRE. These links must be updated to point to the correct Java installation.
• Navigate to the directory (e.g., /opt/CA/WorkloadAutomationAE/): cd /opt/CA/WorkloadAutomationAE/
• Remove the existing, broken symbolic links:
  rm -rf JRE_WA rm -rf JRE64_WA
• Recreate the symbolic links to the correct Java path:
  ln -s /etc/alternatives/jre_openjdk JRE_WA ln -s /etc/alternatives/jre_openjdk JRE64_WA
  
  

Verification:

• Verify the directory structure and links by running: ls -al /opt/CA/WorkloadAutomationAE/
• Ensure the links correctly point to /etc/alternatives/jre_openjdk.
• Attempt to start the services again.

Additional Information

For additional info - refer to JRE Update 

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.