Question
Mastercard Inc
US
Last activity: 25 Jan 2019 14:24 EST
Inactive DB sessions
We use Pega 7.1.8 and Pega 7.2 . We have observed that many sessions are in inactive state on the DB there by creating resource limit issues. These sessions are created by the Pega DB User and shift to inactive and stay in that state for a long time.We have tested shutting down all the Application agents and turning on only Pega OOTB agents, but the inactive session count is not reducing. Our connection pool size is big enough to accommodate the JVMs and users we have.
Has anyone faced this issue. Any particular Pega agent causing this issue ?
***Edited by Moderator Marissa to update platform capability tags****
Cognizant Technology Limited
IN
Hi Viswa,
Hi
Engine creates new requestor whenever a new browser session is being launched with valid credentials. You might have to look at client IP address column to check whether the requestors are being instantiated from different machines or is it same machine if same then validate the number of requestors. If the number of is huge from the same machine, it could be a DDOS attack. This also looks like, application is open in multiple systems and getting refreshed regularly.
Hi Viswa,
Hi
Engine creates new requestor whenever a new browser session is being launched with valid credentials. You might have to look at client IP address column to check whether the requestors are being instantiated from different machines or is it same machine if same then validate the number of requestors. If the number of is huge from the same machine, it could be a DDOS attack. This also looks like, application is open in multiple systems and getting refreshed regularly.
Also you can check last access time coloumn against each requestor to check whether requestor is actively being used by the end-users. Based on their needs they can lower the passivation interval which will passivate the requestors to save memory.