Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Failing to release lock (same user, different requestor)



Users who experience session timeouts attempt to access the work objects again.

When logging into another node with the same operator ID but a different requestor, users are unable to end the other session and unlock the work object.

After pressing Release Lock, the lock is not released. System Pulse is running on all nodes.

Error Messages

Not applicable

Steps to Reproduce

  1. Log into two nodes using the same operator Id, two requestors pops up.
  2. Open a case with requestor 1.
  3. Include requestor 2 to try open the same case.
  4. Click on release lock after the message a displayed.
  5. Retry to open the case (that's where user notice that the case is still locked).

Root Cause

By default, PRPC does not handle the case when different requestor from same user is trying to access the work object in a multi-node environment. 


Either add below entry in prconfig.xml file of each node:

<env name="database/lockcache/enabled" value="false"/>


Create following Dynamic System Setting:

Owning RuleSet : Pega-Engine
Setting Purpose : prconfig/database/lockcache/enabled/default
Value : false
Suggest Edit

Published December 27, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us