Discussion

1
Replies
463
Views
SHIVA2010 Member since 2012 24 posts
Virtusa
Posted: 4 years ago
Last activity: 4 years 4 months ago
Closed

Load balancer has less timeout(30mins) than Pega access group(45mins) thus creating new session

Hi,

we are using load balancer for our 2 Pega nodes. The load balancer is using source address persistence and persistence timeout is 30 mins. In Pega, we have set the access group timeout to 45 mins. so after 30 mins of idle time for a requester, the user session is lost at load balancer and returned login screen. Here i observed 2 things. After load balancer timeout, it deletes the session details from it connection table. so it may select any node for next requests eventhough it comes from existing timeout requester. 
1. so if load balancer selected the node in which our idle requester is in then the requester is continue to work without any issues or being redirected login screen. 
2. If it selects another node then the login is screen is displayed. 

Pega still has the old requester in SMA and when user opens another session, and it created another requester. so we have old requester which became orphan(as the persistance of session has been deleted by load balancer) and new requester for new session. In this case the users will lost thier changes in current screen and they consider the timeout is 45 mins and the Pega ReAuthenticate on timeout feature(which will keep the user in current session and all his work will be avaialble) is being unused as well right. 

so what would Pega suggest in this scenario, 

1. Dont set the persistence timeout at load balancer 

2. When we set the timeout at load balancer then all the Pega access groups should have lesser value for their authentication timeout?

Note: I know pega has pxSessionTimer to alert the user before timeout. 

Moderation Team has archived post
Share this page LinkedIn