SM52: VMC Overview – General Information

The following entries are the general information of SM52 VMC in the SAP system.

VMC Status and Number of VMs

  • VMC is active
    • The VM Container is loaded and is running.
  • VMC is inactive
    • The VM Container is loaded but not running.
  • VMC is not loaded
    • No VM Container set up in the system configuration

Status of the Shared Memory Garbage Collection

  • Not active
    • No SGC is currently activated.
  • Active, VMs should contribute
    • An SGC is activated and is waiting for the (optional) memory release from one or more VMs.
  • Active, VMs must contribute
    • An SGC is activated and is waiting for the mandatory memory release from one or more VMs.
  • Active, release of all non-referenced objects
    • An SGC is activated and releases memory.

VMC Memory Consumption

  • Shared Pool
    • Total size of shared pool (contains all in the following named objects)
  • Global Classes
    • Classes in the Shared Memory of the VMC (shared classes)
  • Global Programs
    • JIT-compiled classes in the Shared Memory of the VMC (shared programs)
  • Global Data
    • Data defined cross-VM ( Shared Closures)
  • Other Global Data
    • Copy-Only Data of Shared Closures
  • Global Admin Data
    • Unique Description, Messages
  • Other Global Data
    • All remaining objects in the shared memory of the VMC (for example, shared locks)
  • Total
    • Total consumption of all four memory classes
  • Memory Usage
    • Percentage usage of the shared pool through allocated memory (in brackets you can see what percentage of the shared pool is actually used)

Table of VMC

  • 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
    • 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
    • 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
    • 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
    • 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.

You May Also Like

Leave a Reply?