Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix issue relate with CollectionUsageThreshold of memory pool #5324

Merged
merged 1 commit into from
Feb 12, 2020

Commits on Jan 9, 2020

  1. Fix issue relate with CollectionUsageThreshold of memory pool

    	- we should only check if the notification for
    	CollectionUsageThreshold need to be fired at the end of
    	the collection, which try to recycle the memory pool.
    	- for BackCompatible mode scavenge does not try to reclaim
    	memory from the whole heap, so we do not fire the notification of
    	CollectionUsageThreshold at the end scavenge.
    	- record the last GC ID for retrieving more detail gcInfo of
    	last GC from J9GarbageCollectorDataMemoryPoolMXBean
    	.getCollectionUsage() getPreCollectionUsage() and
    	isCollectionUsageThresholdExceeded() also match the same rule.
    
    Signed-off-by: Lin Hu <linhu@ca.ibm.com>
    LinHu2016 committed Jan 9, 2020
    Configuration menu
    Copy the full SHA
    ef32c15 View commit details
    Browse the repository at this point in the history