Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Will Cho (Will Cho)
PEGA
Principal System Architect
Pegasystems Inc.
US
Will Cho Member since 2008 160 posts
PEGA
Posted: Jul 18, 2020
Last activity: Jul 20, 2020
Posted: 18 Jul 2020 15:56 EDT
Last activity: 20 Jul 2020 7:44 EDT
Closed

Queue-For-Agent Lock Error

Hi, I'm using Queue-For-Agent method in activity.  Looks like it was queued and processed by standard agent.  But, we're finding this error.  

<pxErrorMessage>Cannot obtain a lock on instance ORG-CS-CSD-WORK GSR-13029, as Requestor H936111A535BF288B53A4D5FABB9FB79D already has the lock</pxErrorMessage>

As a user i'm still working on the work object, so i'm not sure why the standard agent (running every 30 seconds) is trying to grab the lock on the WO.  It does not need to save any information to WO, thus not needing the lock. 

Please help.

 

 

To see attachments, please log in.
Pega Platform 7.2.2
System Administration
Cross-Industry
Lead System Architect

Posted: 4 years ago
Updated: 3 years ago
Posted: 19 Jul 2020 1:07 EDT
Updated: 14 Jun 2021 7:38 EDT
Pavan Kalyan Kanaparthi (kanap2)
PEGA
Senior System Architect
Pegasystems Inc.
IN

In the agent activity are you trying to acquire the lock of the Work Object while using Obj-Open or Obj-Open-By-Handle?

To see attachments, please log in.
Posted: 4 years ago
Posted: 20 Jul 2020 7:44 EDT
Will Cho (Will Cho)
PEGA
Principal System Architect
Pegasystems Inc.
US

No, even when I have no step in the agent activity, this locking error is still happening.

Is this locking done by Pega engine that we can't control?

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice