No one has been able to substantiate the performance impacts on users since I keep getting the same reply that this is only seen in splunk and dynatrace. The PRPushServlet is working per design and is not a concern regarding performance issues.  The way the PRPushServlet works is below. The PRPushServlet attempts to make a websocket connection and if this fails it will revert to longpoll.  It appears in your case it has reverted to longpoll.  The longpoll will make a request and sits idle waiting for a message.  If no message is received them it will time out and initiate the long poll request again. Pega is using the Servlet 3.0 async APIs. The Servlet API provides 2 APIs: suspend and resume. When the long poll is waiting for a response /message the thread is put into a suspend state.  When it is in suspend it clears all resources and allows all other requests to use the thread. If a message arrives for longpoll then it will wake up with a resume and process the message. A thread would then be associated with the request and the message would be sent back to the browser.  This is not blocking longpolling, therefore there is no performance impact.  The dynatrace indicates you are running on jboss which in certain versions does not enable websockets out of the box. I would reccomend you validate your version and enable websockets.  Websockets is a bi-directional communication that runs on top of the HTTP protocol. Once this is enabled you will not see these polling requests, since websockets establishes a single connection at which point all messages are sent through the initial connection.  Steps to enable websockets in jboss: JBOSS EAP 6.4.0 GA and 6.3.0 GA                     Note: JBoss 6.1.0 GA does not support websockets.     To enable the support for websockets we need two changes       1. Modify jboss-web.xml in the war file to enable websockets         In prweb.war/WEB_INF/jboss-web.xml, add below tag         <enable-websockets>true</enable-websockets> just before </jboss-web>       2. Change JBoss to use the NIO connector         Open $JBOSS_HOME/standalone/configuration/standalone-full.xml and change         <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>  to         <connector name="http" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="http" socket-binding="http"/>     This will need our PRPC redeployment as we are changing deployment descriptor (jboss-web.xml)   If you have any questions please let me know.   Thank You. 

 No one has been able to substantiate the performance impacts on users since I keep getting the same reply that this is only seen in splunk and dynatrace. The PRPushServlet is working per design and is not a concern regarding performance issues.  The way the PRPushServlet works is below. The PRPushServlet attempts to make a websocket connection and if this fails it will revert to longpoll.  It appears in your case it has reverted to longpoll.  The longpoll will make a request and sits idle waiting for a message.  If no message is received them it will time out and initiate the long poll request again. Pega is using the Servlet 3.0 async APIs. The Servlet API provides 2 APIs: suspend and resume. When the long poll is waiting for a response /message the thread is put into a suspend state.  When it is in suspend it clears all resources and allows all other requests to use the thread. If a message arrives for longpoll then it will wake up with a resume and process the message. A thread would then be associated with the request and the message would be sent back to the browser.  This is not blocking longpolling, therefore there is no performance impact.  The dynatrace indicates you are running on jboss which in certain versions does not enable websockets out of the box. I would reccomend you validate your version and enable websockets.  Websockets is a bi-directional communication that runs on top of the HTTP protocol. Once this is enabled you will not see these polling requests, since websockets establishes a single connection at which point all messages are sent through the initial connection.  Steps to enable websockets in jboss: JBOSS EAP 6.4.0 GA and 6.3.0 GA                     Note: JBoss 6.1.0 GA does not support websockets.     To enable the support for websockets we need two changes       1. Modify jboss-web.xml in the war file to enable websockets         In prweb.war/WEB_INF/jboss-web.xml, add below tag         <enable-websockets>true</enable-websockets> just before </jboss-web>       2. Change JBoss to use the NIO connector         Open $JBOSS_HOME/standalone/configuration/standalone-full.xml and change         <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>  to         <connector name="http" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="http" socket-binding="http"/>     This will need our PRPC redeployment as we are changing deployment descriptor (jboss-web.xml)   If you have any questions please let me know.   Thank You.