Support Article
Decrement the lock count error in logfile
SA-353
Summary
The following error is observed in the PegaRULES logfile:
2014-07-16 14:00:10,128 [ PegaRULES-Batch-5] [ STANDARD] [Application1:01.01.01] (xternal.mgmt.PRThreadStateImpl) ERROR - Attempting to decrement the lock count for Requestor B0DF31AC59B994EEE85066177E363CBE6 by 1, even though it only holds (at most) 0 lock(s)
Error Messages
2014-07-16 14:00:10,128 [ PegaRULES-Batch-5] [ STANDARD] [Application1:01.01.01] (xternal.mgmt.PRThreadStateImpl) ERROR - Attempting to decrement the lock count for Requestor B0DF31AC59B994EEE85066177E363CBE6 by 1, even though it only holds (at most) 0 lock(s)
Steps to Reproduce
Not Applicable
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. Incorrect logic in the lock manager will sometimes attempt to decrement a lock count that is already at zero. This causes no harm but prints an error to the log.
Resolution
This issue is resolved by hotfix item HFix-6731.
Published March 7, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.