The business process definitions (BPD) for IBM Business Process Manager V7.5 products and other actions fail in a Microsoft SQL database due to a bad driver lock timeout.
The following failure error message is seen: com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded
The wrong lockTimeout value is provided during installation.
Resolving The Problem
In the administrative console, complete the following steps:
- Click Resources > JDBC > JDBC Providers.
- Select the JDBC provider.
- Select the data source and click Custom properties.
- Change the lockTimeout value from 2000 to a larger value. A value of 30000 to 60000 is enough in most cases.
Note: This value is a lock timeout that is specified in milliseconds.This tuning parameter depends on your application usage and design; it might add more lock contention into your application. Through testing you can determine whether errors occur during your normal processing. If you use a Microsoft SQL Server, then the default value is 2000 milliseconds, which is too low. However, for most other database types, default value is between 30 and 60 seconds. Consider setting the timeout value to between 30 and 60 seconds for the IBM Business Process Manager V7.5 products. Value of -1 means there is no timeout.
- Repeat the previous 2 steps for each of the data sources.
15 June 2018