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

PushException occuring on all environments



After disabling PRPushServlet using the prconfig.xml Dynamic System Setting (DSS), multiple PushExceptions are generated in the log for the application server.
The error occur on every interaction performed on the Pega portal. The error displays for the PushException even when the users log out.

Error Messages

com.pega.pegarules.session.external.serverpush.PushException :Push Engine is not yet started or starting has failed.

[] [STANDARD] [ ] [ ] (ervlet.WebAppLifeCycleListener) INFO - Push is disabled!
[] [STANDARD] [ ] [ ] (ervlet.WebAppLifeCycleListener) INFO - MBean registered via WebAppLifeCycle: 9cf973a99efb8b83810b410068730498
[] [STANDARD] [ ] [ ] ( INFO - MBean Management (Web) initialized for WebSphere
[] [STANDARD] [ ] [ ] (ervlet.WebAppLifeCycleListener) INFO - Push Engine will not be initialized, because push enabled: false and servlet registration

Steps to Reproduce

  1. Monitor the application using client tools to track the PRPushServlet invocations.
  2. Set the following DSS to disable the Push feature:

    Owning Ruleset: Pega-Engine
    Purpose: prconfig/server-push/enabled/default
    Value: false

Root Cause

A defect in Pegasystems’ code or rules.
Incorrect message type displayed in the logs.
In Pega 7.2.2, a hotfix was provided. This was because, in the earlier release the messages were ERROR instead of INFO or WARN.
The reason for the notification in DynaTrace was because the Push feature was disabled in the environment and the Presence was enabled.
When there is a change in the Presence record, it is published to subscribers using the Push framework. Since the Push feature was disabled, PushException displayed.
The logging level was changed to WARN when PushException occurred in an attempt to obtain a PushService instance. The type 'Error' would be logged if the Publish failed.


Here's the explanation for the reported behavior:

The log message indicates that the login and logoff events are not published to the browser. This is expected because the the browser Push event is disabled. However, a warning or an information message must display instead of error messages in the logs.  

As a local-change, update to Pega 7.3.1.

Published May 7, 2019 - 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