Question
Kelly Services
US
Last activity: 24 May 2017 6:36 EDT
Property-Set-Stream Is Bringing JVM Down By Utilizing The Whole Heap Memory
Hello All,
I am using Rule-Obj-Corr which is using 4 different data pages which intern call 4 different report definitions.
And in an agent activity, i am using this Rule-Obj-Corr as input to my OOTB activity HTMlToPdf by setting this in property-set-stream method.
So, when i am trying to run this agent activity manually the jvm is getting hunged and it is going to un-responsive state and we cannot able to restart the jvm as well. So when we go and clear the heap memory the the server is getting restarted and again when i ran my agent activity, for the first time it is running and from the second time, it again taking the server down.
So, verified the Pega log files and Pega Alert log file and found nothing. So assuming the property-set-stream that i am putting the whole corr rule into Param.Markup for my OOTB HTMLToPDF activity to create the single pdf is eating up the whole heap.
So, will property-set-stream which is getting set into a parameter for that session will still retain in the heap.
How to clear this and address this and make sure it doesn't eat up the whole heap memory?
Accepted Solution
Kelly Services
US
Thanks for your reply.
The issue is resolved. This was happening not because of the property-set-stream. We have n number or reports being retrieved manually via activity rule, which is making the heap memory filled up. So, instead of fetching all the rows, we are just fetching the count of number of rows by making it summary reports definitions, which make this problem solved. Appreciate your support and help.
Pegasystems Inc.
US
Hi Giri,
Please provide the details regarding the version of Pega that you are using as well as the DB and Application server details.
Review the alert file for Pega0028 alerts indication that GC is having problems reclaiming heap.
Review the memory footprint of the reports as well.
Accepted Solution
Kelly Services
US
Thanks for your reply.
The issue is resolved. This was happening not because of the property-set-stream. We have n number or reports being retrieved manually via activity rule, which is making the heap memory filled up. So, instead of fetching all the rows, we are just fetching the count of number of rows by making it summary reports definitions, which make this problem solved. Appreciate your support and help.