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.

WCC outofmemory issues

book

Article ID: 227764

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

For the last 3 days we have had complaints that users are unable to login to WCC and I have to restart services which seems to clear up the issue.

Environment

Release : 12.0

Component : WORKLOAD CONTROL CENTER

Resolution

If you are seeing OutOfMemory messages on our WCC see the section "Adjust Memory for Services"

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-0-01/administrating/ca-wcc-administration/tune-component-performance.html

If you are still seeing outofmemory errors in the main wcc logs enable the following configuration options in the 
<tomcat>/conf/wrapper.conf (and restart tomcat service to make them effective) and once replicated contact support.

#wrapper.java.additional.16=-XX:+HeapDumpOnOutOfMemoryError     (This line to be uncommented. Please be cautious about this number, we need to increment it, if it is already being used in existing wrapper.conf file)
wrapper.java.additional.17=-XX:HeapDumpPath=<$CA_WCC_INSTALL_LOCATION>/wcc/log/       (To add this line. The <$CA_WCC_INSTALL_LOCATION> to be replaced appropriate to their WCC installation location)

With the above configurations in place and once tomcat service is restarted, when OutOfMemoryError occurs, java will create heap-dumps in the above mentioned location with *.hprof extension.