prPushServlet pooling on accessing Pega app through proxy
Continous prPushServlet pooling occurs when accessing the Pega application through a proxy.
The user has Apache 2.2 server which is Windows based and which does not support WebSockets.
Steps to Reproduce
Below are the reasons for the large number of requests:
- Due to the proxy, HTTP 302 redirect response is received for every request. The next request receives HTTP 200 OK status. Hence, the number of requests is doubled.
- According to Long Polling design, a long polling request is sent to the server every two minutes. During this gap, polling requests (heartbeat) are sent to check if the user is still logged in or has closed the browser/tab so that the server can clear the assigned resources. By default, this request occurs thrice per minute.
Perform the folloiwng local-change:
Add the below line in prconfig.xml to configure the interval setting (for example, the interval value is in seconds; that is, the value is set 120 seconds for an interval of two minutes).
<env name="server-push/client-heartbeat/interval" value="120"/>
0% found this useful