Question
TATA Consultancy Services Ltd
IN
Last activity: 20 Feb 2020 5:05 EST
Agents stop with the exception due to lock not obtained on the work object
Hello, After up gradation of our environment from 7.2.2 to 8.2.3 we are facing an issue in agents. Few agents are getting stopped with the following exception. "QueueForLockedTasksCannot obtain a lock on instance "class instance name xyz" , as Requestor B49PCEEHPSBHDKYQEZ0VELWNXT7QRGA7SA already has the lock". Kindly help us to resolve the issue. Thanks, S.Seetharaman
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
FR
Hello,
Is it a custom agent? Maybe the agent is running on multiple nodes and another instance is already processing? Can you change your design with a Job Scheduler maybe?
TATA Consultancy Services Ltd
IN
Pegasystems Inc.
FR
Right I see,
Maybe you can just add a step to check if the lock can be taken if not exit the activity do nothing and wait. I'm just guessing if the lock is already held by another batch process it might be for a good reason.
Bits in Glass
IN
Hi,
Can you please check whenther lock has been already held for this object already?
As per the error lock has been already held.
Pegasystems Inc.
IN
Hi,
Can you check the below article with similar discussion?
https://collaborate.pega.com/question/requestor-already-has-lock
Thanks
Accepted Solution
TATA Consultancy Services Ltd
IN
Pegasystems Inc.
IN
Thank you for updating your post with the solution. We will mark this post as Answered.
wipro
US
I have a question
In my case OBJ-OPEN by handle is the first step and we have written jump step as when stepstatusfail jump to last step so if lock was not acquired agent jumps to last step of activity.
Now how can i use this Activity clear status?