Customer complained that they are seeing this error intermittently and that WCC is also slow
Error: E131013 Job not collected in WCC. It could mean some problem with monitoring collector.
WCC 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 file above has info like this:
0SECTION TITLE subcomponent dump routine
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)
0SECTION GPINFO subcomponent dump routine
Release : 12.0
WCC collector's Java ran out of memory. Increase the memory allocation to WCC and WCC Collector Java.
Our collector memory default settings are below, in /opt/CA/WorkloadAutomationAE/wcc/collectors/WCC_COLLECTOR/conf/wrapper.conf
With r12 onwards, collector is also 64bit and as you are running out of memory, you can easily increase it to much higher (as long as you have enough memory on the WCC server )
The same can be done to increase regular WCC UI's tomcat memory too:
bump this up to a higher value like:
Of course, with collector + WCC now set to 4GB each, you need at least 10GB free memory on the host before you can use it like this.
Additional performance tuning recommendations are here: https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-0/administrating/ca-wcc-administration/tune-component-performance.html