Issue

User’s session is lost due to an application node shutdown. User attempts to release the lock the prior session holds on a work object. However, the lock does not get released.

Symptoms and Impact

The following initial error displays along with the  End other session to release a lock button:

This case is locked by you in another session.

When the user clicks the button, the initial error displays again, and the lock does not get released.

Steps to reproduce

1. User logs in on App node #1.
2. User opens the work object W-1 and a lock gets created.
3. With user still having a lock on W-1, shut down App node #1.
4. A record remains in the PR_SYS_LOCKS table even after the node is shut down.
5. User logs on to App node #2 and tries to obtain a lock on W-1.
6. Since W-1's lock is still obtained with App node #1, user cannot get a lock. This case is locked by you in another session. error message displays on the screen. However, since the owner of the record is the same operator ID, End other session to release a lock button displays.
7. Even though user clicks the button End other session to release a lock, the lock never gets released. The same error message displays again.

Root Cause

A known limitation in the Pega Platform where the End other session to release a lock button does not release locks established while on another node than the node the user is currently on.

Solution

An enhancement request for the End other session to release a lock button to be updated to release locks established while on other nodes is currently under consideration. However, it has not been assigned to a specific release.