System Agent startup thru systemctl fails and performs systemd-cordedump

Products

• Autosys Workload Automation
• ESP dSeries Workload Automation - System Agent (dSeries)
• Workload Automation Agent

Issue/Introduction

The waae_agent-WA_AGENT.service is failing to stay active. While the ExecStart script returns a success code, the main Java process is triggering a core dump immediately after launch.
Systemd logs show an active: failed (Result: exit-code) status despite the initial '[ OK ]' message from the agent wrapper."

waae_agent-WA_AGENT.service
     Loaded: loaded (/etc/systemd/system/waae_agent-WA_AGENT.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Fri 2026-01-16 15:21:35 CET; 6s ago
   Duration: 409ms
    Process: 2086527 ExecStart=/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/waae_agent-WA_AGENT start (code=exited, status=0/SUCCESS)
    Process: 2086586 ExecStop=/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/waae_agent-WA_AGENT stop (code=exited, status=1/FAILURE))
   Main PID: 2086539 (code=exited, status=0/SUCCESS)
        CPU: 1.005s

Jan 16 15:21:33 server.example.com waae_agent-WA_AGENT[2086527]: [ OK ]
Jan 16 15:21:35 server.example.com systemd[1]: Started waae_agent-WA_AGENT.service.
Jan 16 15:21:35 server.example.com systemd-coredump[2086578] :  [ ] Process 2086541 (java) of user 0 dumped core.

 

Environment

Red Hat 9.x
System Agent 12.1 SP1

Resolution

Add following 2 parameters in /etc/systemd/system/waae_agent-WA_AGENT.service

LimitNOFILE=65536
TasksMax=infinity

Additional Information

• TasksMax=infinity: Prevents the OS from capping the number of threads the JVM can create, which is essential for the Agent's multi-threaded architecture.

• LimitNOFILE=65536: Ensures the Agent has enough file descriptors to manage its logs, spool files, and communication sockets simultaneously.