
You can see the list of the VMs currently instantiated, and the following information for each VM:
|
Column Name |
Meaning and Possible Values |
|
No.: |
Internal number of VM (0, 1, 2, …) |
|
Time |
Time when the VM began processing the last request |
|
WP |
Number of the work process to which the VM is currently assigned (0, 1, 2, … or empty if it is not assigned) |
|
Type |
Usage type of the VM; possible values:
|
|
State |
Current status of the VM; possible values:
|
|
User |
Name of user that started the program just being processed. |
|
Program |
Name of the application program just being processed. |
|
CPU |
Processor time used up to now by the VM. Time format is hours:minutes:seconds:microseconds (hhhh:mm:ss.mmmm) |
|
MB |
Memory space in megabytes currently occupied by the VM. |
|
Debugging |
Current debugging status of the VM; possible values:
|
|
Port |
Number of the port through which the VM is connected to the debugger (8000, 8001, …) |
|
SGC State |
Status of the VM in the event of a shared garbage collection, currently with the addition "waiting", in case the VM itself is waiting for memory to be freed up. The following statuses are possible:
|
There are also additional table columns, which by default are not displayed. They can however be displayed by using the context menu function Show of the ALV Control.
|
Column Name |
Meaning and Possible Values |
|
Information |
An icon signals a special VM status (see below). |
|
Locks |
Number of locks held by the VM. Cross-VM locks are used within the VM Container to synchronize global data. To minimize collisions there are various locks for the individual application areas, and you can tell these locks apart by their names. If a lock is just about to be set, its name is displayed. If a lock has already been set, its name is already displayed. |
|
Trace |
On or Off, depending on whether trace flags are activated. |
|
LWP |
Number of the work process the VM was last assigned to ("Last Work Process"; 0, 1, 2, and so on). This information is useful if, for example, you are searching for the associated developer trace (dev_w0, dev_w1,… ) (see Developer Traces). |
|
Name of the Lock |
Name of the lock last requested. If multiple locks are held, you can see the other locks in the technical information of the VM ( ). Here you can see:
Since locks by their nature are cursory (unless the VM is gets stuck), this information can seldom be seen. |
The first three columns provide more details of the specific state the VM temporarily has. The specific status of a VM is indicated by a background color in its table row in a standard table layout.
A
light blue colored row signals that debugging has been activated for this VM, which means the VM can be connected to a debugger with the next request. The
icon appears in the additional column
Info.
A
yellow colored row means that trace flags have been activated for this VM. The icon
appears in the additional column
Info, and
On or
Off appears in the additional column
Trace.
A
red colored table row means that this VM is holding at least one lock (mutex flag), that is, it exclusively makes use of one or more VMC resources. The icon
appears in the additional column
Info, and On or Off appears in the additional column
Trace.