Posted: 10 Jan 2021 21:28 EST Last activity: 18 Jan 2021 12:33 EST
Users acquiring lock on FW-Work class instance
We are facing an issue in production where oftentimes users are acquiring lock on ORG-FW-AppFW-Work class instance (we do have a blank instance in this class with pzInskey = "NBFC-FW-UWWBFW-Work"). Due to this other users were unable to create any new case until the lock on this instance is released from system locks.
We do verified the logs at the time of instance is locked and below is the exception reported every time. There were few HFixes suggested in pega community to resolve the below timeout exception. However firstly I'm not sure whether this exception can result in acquiring the lock on FW class instance. Please share your thoughts.
[jsse-nio-443-exec-25] [ STANDARD] ( rd.queryexec.SqlQueryExecutor) An error occured on executing the query for the report definition - There was a problem getting a list: code: 0 SQLState: HY008 Message: The query has timed out.
DatabaseException caused by prior exception: com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.
| SQL Code: 0 | SQL State: HY008
***Edited by Moderator: Pooja Gadige to add platform capability tag***
It is causing when user tries to resume work in a timed out SSO session. However, we had a piece of code in HTML Fragment UserWorkForm (referred in harness level) and due to that a blank pyWorkPage with FW-Work class is being initiated in clipboard as soon as the requester logged in and also on all the non work object threads. Since the session is timed out and user is trying to access the task by clicking on Begin button, system treating that as a non work object or default login thread (with FW-Work class) and acquiring a lock on framework class instance upon click of it.