Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JVM heap filling after attempting to Index

SA-24192

Summary



When Admin user attempts to re-index work from the Search Landing Page, the Pega node gets stuck JVM heap fills, with OutOfMemory errors in the PegaRULES logfile.
 

Error Messages



On screen:
Problem occurred while fetching Re index status. Please check your network setup!!!

In PegaRULES logfile:

java.lang.OutOfMemoryError: GC overhead limit exceeded
Caused by: java.lang.OutOfMemoryError: Java heap space
    at com.pega.pegarules.search.internal.es.AbstractIndexer._buildIndex(AbstractIndexer.java:477)
    at com.pegarules.generated.activity.ra_action_pzftsbatchindexingcoordinator_7eb128d96f0f513e2b6513abb6004938.step1_circum0(ra_action_pzftsbatchindexingcoordinator_7eb128d96f0f513e2b6513abb6004938.java:163)


Steps to Reproduce



Use Search Landing page to re-Index all work objects


Root Cause



A defect in Pegasystems’ code or rules.  In the case of a Application with a large Declarative Network, objects are building in the memory of the indexing thread(s).

Resolution



Apply HFix-27737, which disables Declarative processing during indexing.

 

Suggest Edit

Published June 17, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us