Question
Infosys
IN
Last activity: 23 Apr 2025 11:47 EDT
locking issue due to Commit in the end of the resolve flow
Scenario is:
in the Resolve flow there is utility in the last step in that there is a Commitwithouterrorhandling method. it is getting lock issue Error Message: Database-LockFailure-LockLost
Can someone please share your thoughts?
Accepted Solution
Updated: 23 Apr 2025 11:47 EDT
Maantic Inc
IN
In the tracer you need to find out where a commit happened before that made the process to loose the lock. You can try with a Refresh-and-Lock or make the process wait for few seconds before the commit happens. But technically in a flow, Pega takes care of the commit automatically, so ideally you should not required an extra Commit step.
Infosys Limited
IN
The "Database-LockFailure-LockLost" exception in Pega occurs when a process loses a lock on a database record it was trying to update. This can happen due to various reasons, such as another process acquiring the lock, a timeout, or a network issue. To resolve this, you can check the system logs for more details, review your locking strategy, and ensure that your database transactions are efficient and not holding locks longer than necessary. If the issue persists, consider consulting Pega support for further assistance.
Accepted Solution
Updated: 23 Apr 2025 11:47 EDT
Maantic Inc
IN
In the tracer you need to find out where a commit happened before that made the process to loose the lock. You can try with a Refresh-and-Lock or make the process wait for few seconds before the commit happens. But technically in a flow, Pega takes care of the commit automatically, so ideally you should not required an extra Commit step.