VM Overview: Table of VMs (SAP Library - Administration of the VM Container)

VM Overview: Table of VMs

The table body on the overview screen looks like this:

This graphic is explained in the accompanying text

You can see the list of the VMs currently instantiated, and the following information for each VM:

Table of VMs

Name of Column	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: Template: The VM is used as a template for instantiating further VMs. Servlet: The VM processes HTTP requests RFC: The VM processes RFC requests Auto Java: The VM handles internal VMC services periodically Java Test: The VM carries out specific internal tests
State	Current status of the VM; possible values: Starting Up: The VM is just being instantiated and initialized. Stopping: The VM is bring stopped and then deleted. Running: The VM is just processing a program. Waiting: The VM is processing a program, but is just waiting for a resource. In pool: The VM is free for processing a program. Sleeping: The VM has been moved by the program or by the VMC into a in temporary wait state. Wants to Lock: The VM is waiting for a resource to be locked for it.
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: Not Active: The VM is not currently connected to a debugger. Started: The VM is being prepared for the connection to a debugger. Waiting: The VM is waiting for the connection to a debugger. Active: The VM is currently connected to a debugger. Stopping: The VM is closing the connection to the debugger
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: Neutral: The VM has no shared memory to release. Should Contribute: The VM, if possible, should release memory. Must Contribute: The VM absolutely has to release memory. Contributing: The VM is releasing memory right now. Has Contributed: The VM has released memory.

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.

Additional Columns

Name of Column	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 within the VM Container are used to synchronize global data. To minimize collisions, for the individual application areas there are various locks whose names tell them apart. 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).
Lock Name	Name of the lock last requested If multiple locks are held, you can see the other locks in the technical information of the VM (Edit → VM → Technical Info). Here you can see: ● mtx info – a lock already set ● locking mtx info – a requested, but not yet set, lock. 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 This graphic is explained in the accompanying text icon appears in the additional column Info.

A yellow colored row means that trace flags have been activated for this VM. The icon This graphic is explained in the accompanying text 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 This graphic is explained in the accompanying text appears in the additional column Info, and On or Off appears in the additional column Trace.