WebSphere Process Server for z/OS hangs and then times out after you update the LDAP user registry and attempt to view human tasks
You added users to groups that control human task ownership or administration. You add users to groups that control human task ownership or administration. After you update the LDAP user registry, you cannot view the human tasks. After you review the log files, you notice a CWTKE0021W warning message.
The following message is the complete warning message:
CWTKE0021W: Cannot refresh expired people assignment (staff query result)
In the stack trace, you see the following exceptions:
Exception = com.ibm.bpe.api.WorkItemManagerException
Source = com.ibm.task.core.message.RefreshStaffQueryMessage.processMessage
probeid = 109
Stack Dump = com.ibm.bpe.database.TomSQLException:
com.ibm.db2.jcc.am.SqlException: [jcc][3.59.83] T2zOS
exception: [jcc][T2zos]T2zosResultSet.readFetch_:nativeFetch:3045: DB2 engine SQL error, SQLCODE = -904, SQLSTATE = 57011, error tokens = 00C90096;00000304;WPS01DB .WORKI01 .X'00373F' '.X'28' ERRORCODE=-904, SQLSTATE=57011
You exceeded the maximum number of locks that can be held per user The error tokens = 00C90096 for object WPS01DB .WORKI01 means you are using ROW level locking.
Diagnosing the problem
The page lock on the page or subpage that is identified by NAME in the DSNT500I message caused the total number of page locks concurrently held to reach the installation maximum number of page locks (NUMLKUS) that are allowed for a single agent in the system.
Resolving the problem
To resolve this issue, your database administrator can increase or decrease the NUMLKUS value. You need to either increase the number of locks that can be held by a user in zparm or decrease the number of locks that are held by the user. To take these actions, use the following statement:
ALTER ... LOCKSIZE TABLE SPACE or LOCK TABLE
Your database administrator can increase or decrease the numlkus values of the following entities:
Translate this page: