Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Anamika Agrawal (AnnaA890)
Cigna
IT Architect
Cigna
US
AnnaA890 Member since 2014 2 posts
Cigna
Posted: Oct 30, 2019
Last activity: Nov 1, 2019
Posted: 30 Oct 2019 22:18 EDT
Last activity: 1 Nov 2019 11:35 EDT
Closed

Pega 8 Passivation Daemon is taking 8GB heap space

After Pega 8 upgrade, we noticed often running out of memory exceptions. We analyzed the heap dump and saw the following -

The thread java.lang.Thread @ 0x4ed86fd60 PegaRULES PassivationDaemon keeps local variables with total size 8,167,661,984 (54.83%) bytes.

The memory is accumulated in one instance of "java.lang.Object[]" loaded by "<system class loader>".

During this time we are processing a file, which has 10,000 rows.

Additionally an end user was running a slow running large report.

Any ideas?

***Edited by Moderator: Lochan to update platform capability tags***

To see attachments, please log in.
System Administration
Updates

Posted: 5 years ago
Posted: 1 Nov 2019 11:35 EDT
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Hi Anna,

Thank you for posting issue on community.

For understanding this issue in a better fashion, can you please provide PegaRULES log files when this OOM occurred.?

Also, share following-

- from admin studio, share screen print of requestors

- 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice