Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Lock Request Time Out



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| ABC_user - Encountered problem when performing a Commit 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

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.


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

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us