SAP ABAP Data Element SVMCRT_PROF_LGC_REASON (GC Statistics: Reason for the GC)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-VMC (Application Component) Virtual Machine Container
⤷
SVMCRT_ADMIN (Package) VMC Administration and Monitoring

⤷

⤷

Basic Data
Data Element | SVMCRT_PROF_LGC_REASON |
Short Description | GC Statistics: Reason for the GC |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 40 | |
Decimal Places | 0 | |
Output Length | 40 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 5 | Reas. |
Medium | 10 | Reason |
Long | 15 | Reason |
Heading | 20 | Reason |
Documentation
Definition
The following reasons can be specified for a garbage collection (GC).
- "allocation failed": A memory request failed.
- "explicit GC": The GC was triggered by a dedicated Java command, such as System.gc().
- "requested by shared GC": The GC was part of a cross-VM GC.
- "explicit shared GC": The GC was part of a cross-VM GC that was triggered explicitly by an application.
- "local code cache full": The VM local code cache has reached its capacity.
- "class statistic dumped": The GC was performed so that an explicitly requested set of class statistics could be created.
- "gc statistic dump": The GC was performed so that an explicitly requested set of GC statistics could be created.
- "reference trace dumped": The GC was performed so that an explicitly requested list of all object reference chains could be created.
- "unknown reason": The GC was not triggered by any of the specified events.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 710 |