SAP Knowledge Base Article - Preview

3001317 - Adjusting Adaptive Processing Servers’ JAVA options to avoid Full Garbage Collection (Full GCs) with MetaSpace


With the default JAVA options specified for the out-of-box Adaptive Processing Server (APS) and the servers that are created manually by the Administrator, the servers may experience Full GCs immediately after the server Starts and initializes.


‘Full GCs’ is a common Key Performance Indicator (KPI) for JAVA server process performance tuning.

Monitoring a JAVA processes Full Garbage Collection (Full GCs) allows the Administrator to adjust memory settings to allow for better performance and availability.  Avoiding high counts of ‘Full GC’ is a common practice as the JAVA Garbage collection engine halts the process momentarily while the objects are shuffled in-and-out of physical RAM and onto Disk.

Having larger Maximum heap sizes and MetaSpace sizes allows the process to suspend all objects and information into physical RAM avoiding the need to write to disk.



SAP BusinessObjects Business Intelligence Enterprise 4.2 / 4.3 (BI 4.3)


SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Business Intelligence platform 4.3


SBOP, BO, BOE, BI, BI4, BI4.x, BIP, BI4.2, BI4.3, APS_, meatspace, GC, FullGC, FullGCs, JVM, JRE, sap_jvm, , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.