Question

1
Replies
102
Views
JonnyGar Member since 2009 91 posts
BNY Mellon
Posted: 5 years ago
Last activity: 5 years 3 months ago
Closed

Running report pyElapsedStatusTrend causing memory issues?

On v7.1.5, a user ran the OOTB Report pyElapsedStatusTrend multiple times production on v7. This led to an OutOfMemory error on the node, ultimately bringing it down.

Each time it ran it also threw a PEGA0035 alert --

The number of elements in this clipboard list property has exceeded WARN level. Maximum size: 10000 Property reference: pyReportContentPage.pzChartData.pxColumns*

I tried the same thing on QA and saw that the report was taking minutes to respond (and throwing the alert above as well). I will probably file an SR as well.

Have others seen this as well? How can we better contain the collateral damage of long-running reports?

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Reporting
Moderation Team has archived post
Share this page LinkedIn