WCC appears slow, WCC collector does not seem to respond quickly and/or is giving errors "Error: E131013 Job not collected in WCC. It could mean some problem with monitoring collector"
search cancel

WCC appears slow, WCC collector does not seem to respond quickly and/or is giving errors "Error: E131013 Job not collected in WCC. It could mean some problem with monitoring collector"

book

Article ID: 226676

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Users experience that WebUI / WCC is slow and potentially see errors like this in Quick View / Monitoring tab:

Error: E131013 Job not collected in WCC. It could mean some problem with monitoring collector.

Environment

AutoSys Workload Automation

Cause

WebUI Collector is crashing in a loop because it is running out of memory.  $WCC_INSTALL_LOCATION/collectors/WCC_COLLECTOR/log  folder has some files like this too

javacore.20211007.144700.23238.0003.txt

heapdump.20211007.144700.23238.0002.phd

Snap.20211007.144700.23238.0004.trc

 

javacore file above has info like this:

 0SECTION       TITLE subcomponent dump routine
 NULL           ===============================
 1TICHARSET     UTF-8
 1TISIGINFO     Dump Event "systhrow" (00040000) Detail "java/lang/OutOfMemoryError" "Java heap space" received 
 1TIDATETIME    Date: 2021/10/07 at 14:47:36:070
 1TINANOTIME    System nanotime: 5857349378927829
 1TIFILENAME    Javacore filename:    /opt/CA/WorkloadAutomationAE/wcc/collectors/WCC_COLLECTOR/log/javacore.20211007.144700.23238.0003.txt
 1TIREQFLAGS    Request Flags: 0x81 (exclusive+preempt)
 1TIPREPSTATE   Prep State: 0x104 (exclusive_vm_access+trace_disabled)
 NULL           ------------------------------------------------------------------------
 0SECTION       GPINFO subcomponent dump routine
 NULL           ================================

Resolution

  • WebUI collector's Java ran out of memory. Increase the memory allocation to WebUI and the Collector Java

  • Our collector memory default settings are below, in /opt/CA/WorkloadAutomationAE/wcc/collectors/WCC_COLLECTOR/conf/wrapper.conf

wrapper.java.initmemory=256
wrapper.java.maxmemory=1024

  • Ensure the hosting server has enough memory available and increae the maxmemory settings to higher values.  Example:

wrapper.java.initmemory=1024
wrapper.java.maxmemory=2048

  • The same can be done to increase main WebUI's tomcat memory too, via /opt/CA/WorkloadAutomationAE/wcc/tomcat/conf/wrapper.conf

wrapper.java.initmemory=256
wrapper.java.maxmemory=2048

  • Bump the above up to a higher value like:

wrapper.java.initmemory=1024
wrapper.java.maxmemory=4096

Additional Information