Vivek Bhadoria (VivekB14)
Senior MTS
VivekB14 Member since 2013 3 posts
Posted: February 7, 2019
Last activity: February 13, 2019
Posted: 7 Feb 2019 3:48 EST
Last activity: 13 Feb 2019 9:31 EST

Lock not released for the same user with different requestor

When user session dies/accidentally closed and he tries to login from a different node - Pega doesn't handover the workobject lock previously held by this user in the new session/requestor. I am looking at info to understand the logic behind this design for live setups, as userid must be recognisable instead its requestor, which is always transient. It introduces delays and impacts the user experience. Especaily when it happens many hundred times like in our environment. So scenarios where gracious logoff hasn't happened - users will always end up in this situation.

Can someone also let me know how lock cache works as we tried putting unlock logic in our activity which seems to be not working all the time either.

The problem I have highlighted is similar to this support article where suggestion is to disable the lock cache. .

***Edited by Moderator Marissa to add SA-ID to post***

Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.