Following are descriptions of the remote procedure call (RPC) and error counters output by the loadstatus command.
This counter | Counts |
---|---|
Executed Regular Steps |
The number of regular steps completed. |
Executed System Steps |
The number of system steps completed. |
External RPCs |
The number of RPCs that come only from the client. |
Internal RPCs |
The number of RPCs that come only from another Process Engine server (that is, communication to the VWSs process from VWRs, VWKs, vwtool, and others). |
Java™ Remote Method Invocation (RMI) RPCs |
The number of Java API calls that have been processed. |
Object Service RPCs |
The number of RPCs that come from Process Engine servers and clients, and are used to read objects (such as work classes, work performer classes, or instruction sheets) that are contained in BLOb format. |
Work Object Inject RPCs |
The number of calls to the work item inject (create) RPC. |
Queue Query RPCs |
The number of calls to the queue query RPCs. |
Roster Query RPCs |
The number of calls to the roster query RPCs. |
Lock Work Object RPCs |
The number of calls to the lock work item RPC. |
Update Work Object RPCs |
The number of calls to the update (or dispatch) Work Object RPCs. |
Invoke Web Services Instructions | The number of Invoke web service instructions executed. |
Receive Web Services Instructions | The number of Receive web service instructions executed. |
This counter | Counts |
---|---|
Lock work object errors |
The number of times an attempt has been made to lock a work item, and that attempt has failed because the work item was already locked, did not exist, or had been updated since the query was done. If this counter increments excessively, try changing the work performers so that they browse and lock in the same API call (use the "query specifier" APIs), instead of reading the work item in one API call and locking it in another. See Help for Process Development for further information. |
E-mail notification errors |
The number of errors that have occurred while attempting to send an e-mail notification. |
Move work objects duplicates errors |
The number of times an attempt has been made to put a work item into a queue on a different Process Engine server , but the work item already existed on that queue. This error occurs occasionally during normal operation if a work item repeatedly moves between two queues on different Process Engine servers. This error occurs rapidly if:
If this error occurs excessively, use the vwverify utility to Verify the workflow database. |
Move work object to new server errors |
The number of times an attempt has been made to put a work item into a queue on a different Process Engine server, but the Process Engine server or database was unavailable. If this error occurs frequently, check that all Process Engine servers are up and the Process Engine software is running on all servers. Fix any errors reported in the system error logs. See Help for Process Task Manager for more information about event logs. |
Transaction deadlock errors |
The number of times a database transaction has been aborted and retried due to a database deadlock error. If this error occurs excessively, report this condition to FileNet engineering. There is no field remedy for excessive occurrences of this error. |
Database reconnect | The number of times a database reconnection occurred. |
Timer manager update errors |
The number of times the timer software tried to time out a work item, but was unable to do so because the work item was locked or missing. This error occurs occasionally during normal operation when the timer software and a user-defined work performer try to access a work item at the same time. If this error occurs excessively, try restructuring your workflow so that work items do not time out as frequently while they are locked. |
Work objects skipped due to security errors |
The number of times a work item was omitted from the results of a query because the caller did not have read or write access. Excessive numbers of these errors result in lower performance because Process Engine is reading significantly more data than is being returned to the user. This error occurs under the following circumstances:
If this error happens excessively, try allowing more access to work object data via the work class, and possibly restricting access to the work item data via security on queues or rosters. |
Exceed the workspace cache | The number of times the system has had to replace an item in the workspace cache because the cache was full. For more information about adjusting the workspace cache size, see the "WorkSpaceCacheSizeParameter: Cache isolated region workspaces" section in the IBM FileNet P8 Performance Tuning Guide. |
Exceed the isolated region cache | The number of times the system has exceeded the suggested maximum number of cached isolated regions. |