The Memory Leak Algorithm profiles the IBM JVM heap size after a garbage collection has occurred and looks for trends of increased consumption. When an increased is detected, the condition is triggered. The actions allow for this policy are to take JVM heap dumps and/or restart server.
When you create a Memory Leak Condition policy you can choose to create the policy using one of the following three options: Aggressive, Normal, or Conservative.
Attribute Details
level
-
When you create a Memory Leak Condition policy you can choose to create the policy using one of the following three options: Aggressive, Normal, or Conservative.The detection level specifies how aggressively to monitor for memory leasks. An Aggressive policy will be able to detect a pontential memory leak quickly, however will have a greater propensity for falsely identifying a memory leak than a Conservative policy. Conservative policy will have less propensity for false alarms, however will not detect a potential memory leak as quickly as the Aggressive policy would. data type:ConditionLevel default Value:
unspecified
Allowed Values:
AGGRESSIVE
NORMAL
CONSERVATIVE