Question
CGI
GB
Last activity: 15 Aug 2024 6:02 EDT
Case lock is not released after 2 Hrs from workbasket
Hi,
we have configured the expire lock time for a case type to 2Hrs from default time 30mins, but even after 2hrs of idle time the lock is not being released when we try to open the case from workbasket.
What actions does Pega perform on lock expiry? (currently, Lock is not released even after the lock is expired.)
Thanks, Gomathi
Accepted Solution
CGI
GB
Thanks for the details. But as part of the requirement, we have one visibility condition in release lock, so I have removed the logic in visibility condition.
Now it is working fine.
Thanks,
Gomathi
Pegasystems Inc.
GB
@GomathiP16632518 When a lock has expired, it is considered a "soft" lock. This means that another requestor would be able to obtain the lock at that point and process the work object. However, the lock is not automatically released when it expires. The ClusterAndDBCleaner agent includes a step to call pzDeleteExpiredLocks, which deletes System-Locks that expired three or more days ago. If the lock is not being released even after the lock expiry time, it could be due to issues with the multi-node environment or lock caching. You may need to disable lock caching by setting the prconfig setting <env name=\"database/lockcache/enabled\" value=\"false\"/>. Also, ensure that the lock timeout value for child cases is less than the timeout value for the parent case.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
After 30 Minutes working on Case, it is not getting submitted.
You have lost the ability to make this change because a change elsewhere has tak
@GomathiP16632518 When a lock has expired, it is considered a "soft" lock. This means that another requestor would be able to obtain the lock at that point and process the work object. However, the lock is not automatically released when it expires. The ClusterAndDBCleaner agent includes a step to call pzDeleteExpiredLocks, which deletes System-Locks that expired three or more days ago. If the lock is not being released even after the lock expiry time, it could be due to issues with the multi-node environment or lock caching. You may need to disable lock caching by setting the prconfig setting <env name=\"database/lockcache/enabled\" value=\"false\"/>. Also, ensure that the lock timeout value for child cases is less than the timeout value for the parent case.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
After 30 Minutes working on Case, it is not getting submitted.
You have lost the ability to make this change because a change elsewhere has tak
Requestor shown having system locks in All Locks page
Accepted Solution
CGI
GB
Thanks for the details. But as part of the requirement, we have one visibility condition in release lock, so I have removed the logic in visibility condition.
Now it is working fine.
Thanks,
Gomathi