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

System performance degrades in server due to PEGA0101 alert



System performance degrades even when only one requestor is logged in.

Error Messages

PEGA0101 alert

Steps to Reproduce

Not Applicable

Root Cause

The performance degraded due to the following:
  1. PEGA0101 alert was generated when a queue processor failed due to a missing or failed stream node. The stream node is unavailable in the cluster.
  2. The Decisioning Stream Service was required to be running for the Queue Processors. If the Stream Service was not running, the Queue Processors would not be able to Start.
  3. The DType argument was not set for the node.
  4. The pg was empty after the error was present in the log.


Perform the following local-change: 
  1. Add a new stream node to avoid PEGA0101 alerts.
  2. If there is only one node, set it as universal. A universal node supports both the Decision Strategy Manager (DSM) Stream Service and Queue Processor rules.

    For example, use the below setting:


  3. pg is empty after
Alternatively, update to Pega 8.1.2 or Pega 8.2.1.

Published August 15, 2019 - Updated December 2, 2021

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