The document discusses how the Perm and Tenured Heap Spaces metrics are missing from the SAP_GC in Wily and provides a solution. It states that these metrics only appear after the first full garbage collection has occurred and been logged to the monitored trace file. It recommends manually triggering a full GC by setting the -XX:+HeapDumpOnCtrlBreak VM parameter via the Configtool and then creating a stack dump via SAP MMC or jcmon, after which the Tenured and Perm Heap spaces should appear in Wily Instroscope.
Original Description:
Original Title
E2E Perm and Tenured Heap Spaces Missing in Wily SAP_GC - Print View
The document discusses how the Perm and Tenured Heap Spaces metrics are missing from the SAP_GC in Wily and provides a solution. It states that these metrics only appear after the first full garbage collection has occurred and been logged to the monitored trace file. It recommends manually triggering a full GC by setting the -XX:+HeapDumpOnCtrlBreak VM parameter via the Configtool and then creating a stack dump via SAP MMC or jcmon, after which the Tenured and Perm Heap spaces should appear in Wily Instroscope.
The document discusses how the Perm and Tenured Heap Spaces metrics are missing from the SAP_GC in Wily and provides a solution. It states that these metrics only appear after the first full garbage collection has occurred and been logged to the monitored trace file. It recommends manually triggering a full GC by setting the -XX:+HeapDumpOnCtrlBreak VM parameter via the Configtool and then creating a stack dump via SAP MMC or jcmon, after which the Tenured and Perm Heap spaces should appear in Wily Instroscope.
E2E: Perm and Tenured Heap Spaces missing in Wily SAP_GC - Print View
http://www.sapkb.com/print.php?ID=22
E2E: Perm and Tenured Heap Spaces missing in Wily SAP_GC
Article Number: 22 Created On: 2009-10-08 7:36 PM Author: Suresh [subramks@gmail.com] URL : http://www.sapkb.com/question.php?ID=22 Problem: E2E: Perm and Tenured Heap Spaces missing in WIly SAP_GC Solution: As per Wily Troubleshooting guide, these metrics only appear after the first FULL GC has been performed in the monitored system and after this GC has been logged to the monitored trace file (e.g. std_server0.out). How to Trigger a full GC manually: To trigger a full GC manually, set the following VM parameters -XX:+HeapDumpOnCtrlBreak via Configtool. and created a stack dump via SAP MMC (by right clicking on the sever nodes, only for Windows) or jcmon (Unix). After this you should ssee the Tenured and Perm Heap spaces on the Wily Instroscope