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

PushExceptions in Monitoring tool



The DATA-ADMIN-SYSTEM-SETTINGS PEGA-ENGINE!PRCONFIG/SERVER-PUSH/ENABLED/DEFAULT (set to false) Dynamic System Setting (DSS) is disabled and the Servlet in the prweb is commented.

For more information, refer to:

When using a third-party monitoring tool (DynaTrace), PushException occurs in the purepaths (126k entries within two hours).

Error Messages


Steps to Reproduce

  1. Disable Push using a DSS.
  2. Comment the PRPushServlet.
  3. Log in to the Pega application from Designer Studio.

Root Cause

This behavior is as per Pega product design.


Here's the explanation for the reported behavior:

The PushException occurred in the Monitoring tool because it is an internal exception. Internal exceptions are used to handle special conditions. Since the sections attempt to publish or are subscribed to a channel, the monitoring tool identifies such exceptions. The sections retrieve or publish data and the first step is to determine if the Push feature is enabled. This logic is managed by the Internal exception.
Suggest Edit

Published August 15, 2019 - 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