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

Unable to Find Existing Work Item Lock

SA-53443

Summary



The integrated Process Commander Pooled Connection Manager (PCM) displays an error message during a performance load test. PCM is unable to create additional pooled connections causing performance degradation.


Error Messages



Error in the Pega Log file:

[PegaRULES-Batch-68] [STANDARD] [<RULESET>:02.99.99] (MProdSupportMaintenance.Action) ERROR - Error in commit() 
com.pega.pegarules.pub.database.LockFailureException: exception occurred while finding existing lock for <CLASSNAME> <WORKITEM>: code: <none> SQLState: Unable to obtain connection pool semaphore permit (critical) for database "<DBMSNAME>"; none available for reserved and/or common pools.: code: <none> SQLState: <none> Message: <none> Message: <none> 
From: (BEF8595BB4C047D233CAE3EFFF6998057) 
at com.pega.pegarules.data.internal.access.DBLockProviderImpl.findExistingLockInstance(DBLockProviderImpl.java:549) 
at com.pega.pegarules.data.internal.access.LockManagerImpl.checkProviderForLockInstance(LockManagerImpl.java:1267) 
at com.pega.pegarules.data.internal.access.LockManagerImpl.findExistingLockInstance(LockManagerImpl.java:1253) 
... 
Caused by: com.pega.pegarules.pub.database.DatabaseException: Unable to obtain connection pool semaphore permit (critical) for database "<DBMSNAME>"; none available for reserved and/or common pools.: code: <none> SQLState: <none> Message: <none> 
From: (BEF8595BB4C047D233CAE3EFFF6998057) 
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getSemaphoreForConnectionPool(ConnectionManagerImpl.java:1739) 
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnectionFromDatabaseName(ConnectionManagerImpl.java:749) 
...



Steps to Reproduce



Start a Performance Load Test.


Root Cause



When the hotfixes (HFix-40131, HFix-35519, HFix-35082, and HFix-35066) used earlier for the integrated Pega JDBC PCM were analyzed, it was found that an incorrect Java method was used when pooled connections were returned to PCM.  Therefore, these connections were abandoned.


Resolution



Apply HFix-41806.

Published January 31, 2019 - 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