Authentication errors |
The number of authentication errors that are
logged because of an improper security level. |
Authentication token timeouts |
The authentication token for the user that timed
out. In most cases, the token refreshes automatically. Many tokens
can indicate a security issue. |
Database reconnect |
The number of times a database reconnection
occurred. |
Email notification errors |
The number of errors that occurred while the
server was attempting to send an email notification. |
Lock work object errors |
The number of times an attempt was made to lock
a work item, and the number of times that the attempt failed because
the work item was already locked, did not exist, or was 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. For more information, see
the Help for Process Development. |
Object Service Entry Deleted |
|
Timer manager update errors |
The number of times the timer software attempted
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,
restructure your workflow so that work items do not time out as frequently
while they are locked. |
Transaction Deadlock Errors |
The number of times a database transaction is
canceled and retried because of a database deadlock error. If this
error occurs frequently, report this condition to IBM® Software Support. There is no field remedy
for frequent occurrences of this error. |
Work objects skipped because of security 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 frequently,
restructure your workflow so that work items do not time out as often
while they are locked. 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 more data than is being returned
to the user. This error occurs under the following circumstances:- A record is read from the event log, but the user does not have
read access as defined in the work class for the event log.
- A record is read from a queue, but the user does not have read
or write access as defined in the work class for the work item.
- A record is read from the roster, but the user does not have read
access as defined in the work class for the roster record.
If this error happens frequently, allow more access rights to
work object data with the work class, and possibly restrict access
to the work item data with security on queues or rosters. |