ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

AutoSys 12.0 upgrade script fails with a Java Out of Memory error

book

Article ID: 199238

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

AutoSys 12.0 upgrade script fails with a "java/lang/OutOfMemoryError" during the EEM validation steps.

Cause

This issue can occur where the EEM server has a very large number of policies. The InstallAnywhere installer runs out of Memory Heap during validation.
By default it runs with 134m of Max Memory Heap.

Environment

mRelease : 12.0

Component : AutoSys Workload Automation

Resolution

The installer uses InstallAnywhere which provides the option to set Java Max Memory on the command line when executing the installer. 

Example:

./install.bin -jvmxmx 250m

Set this is to a higher value to avoid the OutOfMemory error.

Additional Information

Broadcom reproduced the issue internally with 5000+ policies in EEM. 

It was sufficient to set the java max memory to 200m in that test case to overcome the out of memory error.