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. |
Java RPCs | The number of workflow Java API remote calls that have been processed by the workflow server. |
Object Service RPCs | The number of RPCs that come from workflow 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. |
E-mail notification errors | The number of errors that have occurred while attempting to send an email notification. |
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 an IBM support representative. 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 workflow
system 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 through the work class, and possibly restricting access to the work item data through security on queues or rosters. |
Exceed the workspace cache | The number of times the system exceeds the suggested maximum number of cached workspace. Additional workspace is added to the cache when necessary. |
Exceed the isolated region cache | The number of times the system exceeds the suggested maximum number of cached isolated regions. |