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.
Pegasystems
IN
Hi Jon,
How many records is it returning for you in QA and Production? I am assuming you did not get a PEGA0005 alert so the query is running in the given amount of time but the post processing of the results is taking a lot more time and memory. Would it be possible to reduce the number of records returned? In 7.1.7 there is support for HAVING clause as well to help reduce the records returned to Pega 7 platform from the DB.
-Rajiv