Process services counters

  • The USER > Threads subsections include "Daemon Threads" and "remote procedure call Threads". The subsection tracks the threads for the virtual server process.
    • Daemon Threads - Each daemon records the number of iterations that are completed. The daemons include Vwisi, vwnotify, vwtime, vwusersync, and vwtran. The duration and item count for each thread is recorded under the named daemon thread.
      • Duration – Records the amount of time that it takes to complete the iteration.
      • Item Count – The number of items that are processed.
    • Remote procedure call threads – The Thread information that is recorded for this heading are the threads that handle incoming remote procedure calls.
      • Active – A snap shot of active remote procedure call threads.
    • Outgoing remote procedure calls - There are two outgoing remote procedure call categories: "CE RPCs" (Content Platform Engine) and "DBExecute Stored Procedure". Outgoing remote procedure calls are located under USER and under the repository name and region number.
      • Content Platform Engine remote procedure calls are called internally by the workflow systems server. The name of the Content Platform Engine remote procedure call displays when it is called, and counters under the remote procedure call name record the number of completed remote procedure calls. Each remote procedure call duration and the number of items that are processed are recorded.
        • Duration - The time required to complete the remote procedure call.
        • Item count- The total number of items.
      • DBExecute stored procedure - Records the number of completed stored procedures.
        • Duration – The amount of time to complete the stored procedure.
Dashboard path: HostName > FileNet CA > USER > DatabaseConnection > Database
Database counters
Property Description
Connections Closed Number of close connection requests.
Connections Open Failed Number of open connection request failures.
Connections Close Failed Number of close connection requests that failed.
Java™ RMI remote procedure calls The amount of Java API calls processed.
Transactions completed Number of completed transactions.
Transactions Abort Number of canceled transactions. A small percent (less than 1%) is normal.
Transactions Failed Number of failed transactions.
Statements Executed Number of statements that are run.
Statements Failed Number failed. A small percent is normal on system startup.
Statements Open Failed Number of statement open failures.
Statements Close Failed Number of statement close failures.

Server counters. Server counters are split into two sections; Activities and Errors:

Dashboard path: HostName > FileNet CA > USER > DatabaseConnection > Server Counters > Activities
Activities
Property Description
Client RPCs The number of Java API calls that are processed.
Exceed the Isolated Region Cache The number of isolated regions cached that exceed the default 5 or the value that is set by IsolatedRegionCacheSize.
Execute Regular Steps The number of regular steps that are completed.
Execute System Steps The number of system steps that are completed.
Flush Object Service Cache Adds item to count when the object service data is flushed from cache.
Flush User Cache Entry Counts the number of user cache entries that are flushed.
Invoke Web Services Instructions The number of Invoke Web service instructions that ran.
Lock Work Object The number of calls to the lock work item remote procedure call.
Object Service Entry Deleted Counts removal of an object service entry from cache.
Object Service RPCs The number of remote procedure calls that come from 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.
Queue Queries The number of calls to the queue query remote procedure calls.
Receive Web Services Instructions The number of Receive Web service instructions that ran.
Roster Queries The number of calls to the roster query remote procedure calls.
Update Work Object The number of calls to the update (or dispatch) Work Object remote procedure calls.
Work Object Launched The number of calls to the work item inject (create) remote procedure call.
Dashboard path: HostName > FileNet CA > USER > DatabaseConnection > Server Counters > Errors
Errors
Property Description
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.