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

Complete appservers are down



OutOfMemoryErrors occurs in Pega 7.2.2 system's batch nodes.

Error Messages

java.lang.OutOfMemoryError: Java heap space

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment.

The evidences collected so far point to a sizing problem affecting batch nodes.

The amount of threads and Listeners running concurrently can lead to excessive memory pressure. This can be exacerbated by any slowdown occurring while handling those requests due to increased response time from external services for example, Databases, Remote Services, and so on.

Allocated heap (4GB) is too small compared to the actual load observed on the system.

Pega 7 Platform Installation Guide for WebSphere and DB2-LUW available at the link below recommends an heap size between 4 and 8 GB but larger heaps are advisable when the application allow a high number of concurrent tasks:


Make the following changes to the operating environment:
  • Increase the heap size for batch nodes. In doing so ensure to leave at least 4 GB of free memory for the Operating System, buffering and external processes.
  • In the medium term evaluate the opportunity to add additional batch nodes to distribute the load.

Published May 6, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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