Jcollector is dying and restarting based on the sysedge.log file:
*run_plugin_callback(): PERFORMANCE_WARNING: Plugin callback took more than 31 secs! Plugin: 'C:\Program Files\CA\SystemEDGE\plugins\svcrsp\svcrsp.dll'
* Performance problem detected (monitoring cycle). Elapsed time 31.293010s). SystemEDGE may not be responding to SNMP queries during that time.
*0016181 2019-06-12 08:14:21.66 [W]-1afc- svcrsp/srm-col.c[82] : check_collector(): Collector died, restarting.
0016182 2019-06-12 08:14:21.66 [I]-1afc- svcrsp/srm-col.c[448] : SASetJcollectorEnv(): AWSCOMM_DIR is 'C:\Program Files\CA\SystemEDGE\bin'.
0016183 2019-06-12 08:14:21.66 [I]-1afc- svcrsp/srm-col.c[208] : invoke_collector(): Creating jcollector process with the following command: '"C:\Program Files\CA\SystemEDGE\jre\bin\javaw.exe" -Xrs -Xmx768m -Djava.class.path="C:\Program Files\CA\SystemEDGE\plugins\svcrsp\nis.jar";"C:\Program Files\CA\SystemEDGE\plugins\svcrsp\jcollector.jar" jcollector.jcollector -u -k3131 -loglevel=2 -lognum=1 -logsize=1024 -logfile="jcollector.log" -p"C:\Users\Public\CA\SystemEDGE\port1691\plugins\svcrsp" "C:\Program Files\CA\SystemEDGE\plugins\svcrsp"'.
0016021 2019-06-12 07:37:12.89 [W]-1afc- svcrsp/srm-config.c[1183] : cf_write_line(): When writing the config file, the line #30096 was skipped, because it was longer than the buffer of 2 characters.
Release : 12.9
Component : SESRM - SERVICE RESPONSE MONITOR AIM
1. Download the Jcollector_6Feb.zip file attached on this article.
2. Stop the SystemEDGE agent
3. Make a backup of the original C:\Program Files\CA\SystemEDGE\plugins\svcrsp\jcollector.jar file
4. Extract the Jcollector_6Feb.zip file and place it in the C:\Program Files\CA\SystemEDGE\plugins\svcrsp\ directory5. Start the SystemEDGE agent