Support Article

Lock request time out period exceeded when running batch process



When running a batch process that takes files as input and updates work objects based on that, sometimes it fails on some files with a lock request time out period exceeded error.

Error Messages

2017-04-18 19:45:23,999 [default-threads - 27] [ STANDARD] [ ] [ your_app:01.01.01] ( internal.access.DatabaseImpl) ERROR JMS|your_class|Services|your_service|A150F92378B6D5941700AA6D9293F1428 - Encountered problem when performing a Commit Lock request time out period exceeded.

Steps to Reproduce

Drop the files for the batch intake process.

Root Cause

A defect or configuration issue in the operating environment.

After reviewing the alert log for this time period, it was clear that the database was having trouble handling the all of the transactions associated with this batch processing, particularly based on the number of Pega0026 alerts thrown.


Make the following change to the operating environment:

After making adjustments to the connection pooling with no success, it was discovered that the server hosting the database was only allocated 8GB of RAM.

After increasing this to 16GB, the issue did not reoccur.

Published May 11, 2017 - Updated June 5, 2017

Have a question? Get answers now.

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