SystemEDGE 6.3 Excessive SRM Logs Prints
search cancel

SystemEDGE 6.3 Excessive SRM Logs Prints

book

Article ID: 279286

calendar_today

Updated On:

Products

SystemEDGE Agent

Issue/Introduction

After upgrading SystemEDGE from 5.9 to 6.3 we've noticed the jcollector.log for SRM/SA AIM has a non-event entry for each pass as critical.

The svcrsp.cf file has loglevel = 2 (warning) which is the default.

This is the same setting that was used for 5.9 which didn't generate a non-event entry as critical.
 
jcollector.log
[LOG_CRITICAL][2024-02-09 09:09:55:103][Thread:main][Pass #0]: Pass 0 started.
[LOG_CRITICAL][2024-02-09 09:10:25:103][Thread:main][Pass #1]: Pass 1 started.
[LOG_CRITICAL][2024-02-09 09:10:55:103][Thread:main][Pass #2]: Pass 2 started.
[LOG_CRITICAL][2024-02-09 09:11:25:103][Thread:main][Pass #3]: Pass 3 started.
 
The log has hundreds of non-event critical events.

Resolution

  • Defect DE591951 is created to address the excessive log prints.

  • This will be fixed in SystemEDGE 6.4 (GA date TBD)