Support Article

Push Engine is not yet started or starting has failed

SA-43512

Summary



This issue occurs in Pega 7.2.2 on WebSphere Application Server 8.5 and Oracle Database 12c.

After disabling the PRPushServlet using the prconfig.xml Dynamic System Setting, users see many PushExceptions in the log for the application server, com.pega.pegarules.session.external.serverpush.PushException :Push Engine is not yet started or starting has failed. These errors are thrown on every interaction that users perform in Pega portals. Even when users log out, these errors are thrown for the PushException.

Because of these error messages, users think that the PushServlet functionality is not yet completely disabled.

Error Messages



2017-07-18 00:16:56,145 [.PRPCWorkManager : 6] [ STANDARD] [ ] [ PegaRULES:07.10] (e.PresencePublishEventListener) ERROR - publishForPresence() : Failed while publishing the presence data Push Engine is not yet started or starting has failed.
2017-07-18 00:21:58,540 [.PRPCWorkManager : 3] [ STANDARD] [ ] [ PegaRULES:07.10] (e.PresencePublishEventListener) ERROR - publishForPresence() : Failed while publishing the presence data Push Engine is not yet started or starting has failed.


Steps to Reproduce

  1. Monitor the application using client tools to track the PRPushServlet invocations.
  2. Disable the Push feature by setting the following Dynamic System Setting:
    Owning Ruleset: Pega-Engine
    Purpose: prconfig/server-push/enabled/default
    value: false
  3. Review the logs and see the errors for the PushEngine.


Root Cause



A defect in Pegasystems’ code or rules whereby the wrong type of message appears in the logs

The log message indicates that the login and logoff events are not being published to the browser. Because the user has disabled the browser push event, this is expected.
However, instead of the error messages that appear in the logs, the messages should be warning or information messages.

Resolution

This issue was determined to be a product enhancement request.

​Users can ignore these error messages. In the future, these error messages will be replaced with warning or information messages.

Suggest Edit

Published September 13, 2017 - Updated October 8, 2020


100% found this useful

Have a question? Get answers now.

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