
In the top screen area of the process overview you can display an information area or an enhanced information area. This info area is already displayed in the default setting. If this is not the case, you can display the information area by choosing .
Entry |
Meaning |
|---|---|
Time |
Date, time (hour:minute:second) |
Total Number of Processes |
Total number of configured work processes |
|
For each configured work process type, the following information is displayed:
Example
Line Dialog 16 / 9 (total / free), average load = ( 8,084 / 10,495 / 7,062) means that 9 out of 16 dialog work processes are currently free. Eight processes were fully utilized over the last minute (this corresponds to 50% utilization), 10 in the last 5 minutes, and 7 in the last 15 minutes. So over the course of the last 15 minutes the workload increased initially and then tailed off again. |
Configurable |
Sum of configurable and dynamic work processes |
In addition to the standard infor area, the enhanced info area contains the following lines:
| Entry | Meaning |
|---|---|
Blockade handling |
This means that the dispatcher has created an additional work process for blockade handling (since the start or the last reset). Standby work processes that were activated temporarily are included. |
| Preemptions | This means that the processing of a request was interrupted because of a request with a higher priority. Processing is continued as soon as possible. |
| Reconnects | Means that work processes temporarily closed the connection to the database during a system upgrade, and are now reopening it. |
| Trace is active | Means that the trace is activated. This line explains why work processes in the process overview have the status yellow. |
| Deadlocks | Means that all dialog processes have the status HOLD, and dynamic work processes cannot be started or there are no standby work processes. In this case a snapshot is created and any actions still running are canceled. |
| Work processes are reconfigured. | The configuration of work processes can be changed dynamically by operating modes and other mechanisms. If a work process type (e.g. background processing) is changed from n to 0 processes, this application server can no longer execute the requests after a reconfiguration. To avoid terminations and errors, the service display is first adjusted (e.g. visible in transaction SM51), then maintained for a period, and then only after this are the work processes configured. This line makes the temporary continuation with the old configuration visible. |
| DB reconnect is executed. | Means that not all work processes have executed a requested database reconnect. Note the status in the column for DB reconnect status. |
| ASCS not available | The ASCS instance is not available. During Rolling Kernel Switch (RKS) there is the phase in which the ASCS instance is restarted; this is visible in this column. |
| The AS instance was suspended | The AS instance was suspended. So that no error occurs during the rolling kernel switch (RKS), the AS instances are suspended for a short time. During this time all services that require the ASCS instance (e.g. for internal communication through the message server) are stopped. |
| Snapshots | In the info area the number of snapshots that were created since the last start are displayed. A snapshot is an archive in which all important information about the status of the application server at any given time is stored. A snapshot is primarily used to simulate and interpret the status of the application server at a given time. |
| Signal handler timeouts | If a work process is no longer responding, signals are used to attempt to interrupt the current action. If this does not work, a signal handler timeout occurs. As a consequence the work process is canceled. |