SQLState 25P02 on lock check
SummaryOn running a campaign on a system using a Postgre database, the log file displays an error message. The error message has a value for SQL Inserts which is the name for a lock.
Error MessagesERROR - Problem executing lock check
com.pega.pegarules.pub.database.DatabaseException: Problem executing lock check: code: 0 SQLState: 25P02 Message: ERROR: current transaction is aborted, commands ignored until end of transaction block
SQL: select pxOwnerId as "pxOwnerId", pxUpdateOperator as "pxUpdateOperator", pxUpdateOpName as "pxUpdateOpName", pxExpireDateTime as "pxExpireDateTime", pxUpdateDateTime as "pxUpdateDateTime", pxLockHandle as "pxLockHandle", pxCreateDateTime as "pxCreateDateTime", pxUserHost as "pxUserHost" from pegadata.pr_sys_locks where pzInsKey = ?
SQL Inserts: <OutboundMasterAgent_Lock>
Steps to Reproduce
Run a campaign on a system using a Postgre database.
A defect in Pegasystems’ engine code. The database connection is reused instead of using a fresh connection.
Published June 9, 2017 - Updated August 7, 2017