Discussion
Cognizant
IN
Last activity: 25 Jun 2021 10:38 EDT
PRPushServlet Design Issues- Performance Impact
In PRPC7.2 PEGA engineering Team enhanced Push Notification feature, In order to provide this functionality Pega Implemented PRPushServlet
And in Pega EAR file, by default this PRPushServlet don't added in web.xml file .
Defect#:RULE ENGINE performing heart beat functionality for PRPushServlet for every 30 and pile up asynchronous transactions threads which will run up to 60 seconds and causing major performance impact by consuming 40% of JVM resources. And these long running transactions will not capture in pega-alert or log file .
You might possibly see the info log as "com.pega.pegarules.session.external.serverpush.PushException : Push Engine is not yet started or starting has failed".
So far this issue is not artifact in any pdn community, but this one is a critical bug which impact JVM resources and performance.
I opened the SR , SR-B57948 on 6/26.
So far pega provided the work around solution which is applicable for all PRPC7.2 ,PRPC7.3 VERSIONS.
if your application don’t require Push Notification functionality , then add below DSS setting to disable PRPushServlet transactions as below
“prconfig/server-push/enabled" = false
The fix only suppress the transactions which are taking 60 seconds and piling up the threads on every 30 seconds, but it can’t suppress the PushNotification heartbeat.
since this push notification feature is an optional so that requesting team to disable PRPushServlet events in later 7.3 releases, and provide switch to turn on when it required as part of DSS.
***Updated by moderator: Lochan to tag enhancement ID***
Pegasystems Inc.
IN
Hello!
Thank you for posting on PSC. I understand that you are submitting an enhancement to the product for - disable PRPushServlet events in later 7.3 releases, and provide switch to turn on when it required as part of DSS.
With this understanding, I have submitted an enhancement request on our internal portal. I have updated the request ID under the Related Support Case Number field. Please refer that to your Pega Account Executive for next steps.
Regards,
Pegasystems Inc.
US
I have posted a Pulse note on FDBK-22804.
When the related Support Articles are published to the PDN, I will cite them in this discussion.
Updated: 25 Jun 2021 10:38 EDT
Pegasystems Inc.
US
SR-B57948 generated SA-41495, which is no longer published externally.
However, it did originally cite related SAs:
Indirectly related to SA-41495 is SA-43512, which describes the misleading error messages in the logs that might appear when you disable the application server Push feature:
SA-43512, https://collaborate.pega.com/question/push-engine-not-yet-started-or-starting-has-failed-error-logs
(I have asked the Pega SMEs for a work object# on the generally referenced product enhancement. When I get it, I will update this SA.)
You might also find SA-40421, https://community.pega.com/support/support-articles/upgraded-722-browser-often-hangs-and-needs-refresh-f5. This SA might be useful when disabling the application server Push feature is not feasible for a given Pega environment. Note that this SA pertains to the Tomcat application server. If you are using another application server, check its version, upgrade options, and documentation.