High CPU usage and log access failures in Workload Control Center (WCC)

Products

• Autosys Workload Automation

Issue/Introduction

The Workload Control Center (WCC) server experiences continuous OpenJDK high CPU spiking and failures when attempting to access logs. These symptoms often correlate with out-of-memory issues within the Java process, causing the Web UI to become unresponsive or slow.

Environment

Autosys Workload Automation Release 12.1.01 and higher
Workload Control Center (WCC)
Windows Operating System

Cause

The issue is typically caused by insufficient JVM memory allocation for the WCC services and a restricted message queue size. When the application handles a high volume of data or concurrent requests, the default 2GB memory limit is exceeded, leading to excessive garbage collection (CPU spikes) and eventually "java.lang.OutOfMemoryError" in the logs.

Symptoms:

• High CPU usage attributed to the OpenJDK process.
• Log access failures in the WCC Web UI.
• Error CAUAJM_E_10010 appearing during operations.
• java.lang.OutOfMemoryError in WCC logs.

Resolution

Follow these steps to increase the memory allocation and adjust the environment variables to resolve performance issues.

Increase JVM Memory Allocation

1. IMPORTANT: Ensure you have enough freely available memory to accomodate an increase!
2. Navigate to the WCC configuration directory: ####\Program Files\CA\WorkloadAutomationAE\wcc\tomcat\conf.
3. Open the wrapper.conf file in a text editor.
4. Locate the memory parameters and increase them from the default values. A value of 16GB is recommended for high-load environments:
   • wrapper.java.initmemory=4096
   • wrapper.java.maxmemory=16384
5. Restart the following Windows services for the changes to take effect:
   • CA-wcc
   • CA-wcc-services

Adjust Message Queue Size (Windows)

1. Open the Start Menu and search for "Environment Variables."
2. In System Properties > Advanced, click Environment Variables.
3. Under System variables, click New.
4. Set the Variable name to MB4Q and the Variable value to 64 (or 128 for larger environments).
5. Click OK to save.
6. Restart the server for the change to take effect.

Additional Information

• If performance does not improve, refer to AutoSys and WCC Performance Tuning Best Practices.
• To speak with a customer representative or a Support Engineer, see Contact Support.