Full report generation under Report Generation Services remain High in System Status page and queue size does not appear to decrease

Products

• CA Performance Management - Usage and Administration

Issue/Introduction

Full report generation under Report Generation Services remain High in System Status page and queue size does not appear to decrease.

We see this exception in DM logs when sending an email:

    INFO   | jvm 2    | YYYY/MM/DD HH:MM:SS | Exception in thread "EmailJobTaskThreadPool-Thread-77" org.springframework.context.NoSuchMessageException: No message found under code 'email.job.failure.to.send.email' for locale 'en_US'.
    INFO   | jvm 2    | YYYY/MM/DD HH:MM:SS |     at org.springframework.context.support.AbstractMessageSource.getMessage(AbstractMessageSource.java:155)
    INFO   | jvm 2    | YYYY/MM/DD HH:MM:SS |     at com.ca.im.portal.dm.scheduling.email.EmailJobTask.run(EmailJobTask.java:262)
    INFO   | jvm 2    | YYYY/MM/DD HH:MM:SS |     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    INFO   | jvm 2    | YYYY/MM/DD HH:MM:SS |     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    INFO   | jvm 2    | YYYY/MM/DD HH:MM:SS |     at java.lang.Thread.run(Thread.java:748)

Cause

Defect: DE495327

Environment

Release : 20.2

Component : IM Reporting / Admin / Configuration

Resolution

This issue has been fixed in DX Netops Performance Management 20.2.9:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/20-2/release-notes/fixed-issues.html

Symptom: The report generation service resource load grows when it is unable to get failed schedule email task messages.
Resolution: Fixed the resource growth with the report generation service resource load grows when it is unable to get failed schedule email task messages.
(20.2.9, DE495327, 32572242)

Additional Information

Workaround:

Navigate to:

http://<CAPC>:8181/pc/center/admin/debug/attrs

Change:

PDF.Full.Max.Concurrent to 2

This will cause the system to generate two new threads and start processing the report queue.

Once the queue is processed, set this back to 1.