Discussion

3
Replies
4327
Views
Bhagath_Vasireddy Member since 2015 4 posts
Cognizant
Posted: 3 years ago
Last activity: 3 years 1 month ago
Closed

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***

System Administration SR Exists
Moderation Team has archived post
Share this page LinkedIn