HPjmeter 4.3 User's Guide

Table 10 Fields Captured in GC Log Data When Using -Xverbosegc print options (continued)
◦ 13: Last ditch collection
◦ 14: GC Locker-Initiated GC
◦ 15: Heap Dump Triggered GC (HP implementation)
◦ 16: Heap Dump Triggered GC
◦ 17: Heap Inspection Initiated GC
• When %1 is equal to 3, %2 indicates that a complete background, concurrent mark and sweep GC has
occurred. Reasons for the GC are given as:
◦ 1: Occupancy > initiating occupancy
◦ 2: Expanded recently
◦ 3: Incremental collection will fail
◦ 4: Linear allocation will fail
◦ 5: Anticipated promotion
◦ 6: Incremental CMS garbage collection
• When %1 is equal to 4, %2 indicates that an incomplete background, concurrent mark and sweep GC has
occurred as a result of exiting after yielding to foreground GC. The form for this data set is given as n.m
where n is the GC reason as follows:
◦ 1: Occupancy > initiating occupancy
◦ 2: Expanded recently
◦ 3: Incremental collection will fail
◦ 4: Linear allocation will fail
◦ 5: Anticipated promotion
◦ 6: Incremental CMS garbage collection
and m indicates the background CMS state when yielding, as follows:
◦ 0: Resetting
◦ 1: Idling
◦ 2: Initial marking
◦ 3: Marking
◦ 4: Final marking
◦ 5: Pre-cleaning
◦ 6: Sweeping
◦ 7: Resizing
◦ 8 Abortable pre-cleaning
96 Analyzing Garbage Collection Data