Support Article
Lock Request Time Out
SA-18708
Summary
After upgrade from Prpc 5.5 to Pega 7.1.8, LockRequest Timed out errors intermittently appear screen and in logs.
Error Messages
[ WebContainer : 1] [ Developer] [yAdminColes:03.01.01] ( internal.access.DatabaseImpl) ERROR uat.pega.lga.wan|xx.xxx.xx.xx ABC_user - Encountered problem when performing a Commit
com.pega.pegarules.pub.database.DatabaseException: Lock request time out period exceeded.
Steps to Reproduce
Setup and configure infra as below, issue is intermittent and seeing the issue while navigating to the second screen from first screen. Migrate from Pega 5.5 SP1 to Pega 7.1.8.
Websphere 7
SQL Server 2008 R2
AIX
Root Cause
A defect or configuration issue in the operating environment. This error is thrown if a lock timeout is configured on the JDBC datasource in Websphere, and that timeout is exceeded by a query needing to get a lock on a table. Query was trying to merge updates into Work table, which is quite busy and on occasions had to wait a bit longer in which case this error was thrown. Pre upgrade, this timeout was not in place.
Resolution
Make the following change to the operating environment:
Set the "lockTimeout" on the JDBC datasource to Pega schema defined in Websphere to be reset to "-1" (no timeout).
Published January 31, 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.