282 GcPauseRatioRule_RULE_NAME=GC Pauses
283 GcPauseRatioRule_RULE_TEXT=Application efficiency was affected by GC pauses.
284 # {0} is a percentage, {1} is a timespan, {2} is a timestamp, {3} is a percentage
285 GcPauseRatioRule_RULE_TEXT_LONG=The highest ratio between garbage collection pauses and execution time was {0} % during {1} starting at {2}. The garbage collection pause ratio of the entire recording was {3} %.
286 GcPauseRatioRule_RULE_TEXT_RECOMMENDATION=Pause times may be reduced by increasing the heap size or by trying to reduce allocation.
287 GcPauseRatioRule_RULE_TEXT_OK=Application efficiency was not highly affected by GC pauses.
288
289 GcLockerRule_CONFIG_WARNING_LIMIT=GC locker ratio limit
290 GcLockerRule_CONFIG_WARNING_LIMIT_LONG=Warning limit ratio between number of garbage collections caused by GC locker and total garbage collections
291 GcLockerRule_TEXT_NA=No GC information events found.
292 GcLockerRuleFactory_RULE_NAME=GCs Caused by GC Locker
293 # {0} is a percentage
294 GcLockerRuleFactory_TEXT_INFO=The GC Locker caused {0} of the garbage collections.
295 GcLockerRuleFactory_TEXT_INFO_LONG=Garbage collections caused by the GC Locker indicates that the runtime ran a lot of JNI code. To avoid this decrease the time spent in JNI.
296 GcLockerRuleFactory_TEXT_OK=The GC Locker did not cause any garbage collections.
297 GcStallRule_RULE_NAME=GC Stall
298 GcStallRule_TEXT_OK=No indications that the garbage collector could not keep up with the workload were detected.
299 General_CONFIG_CLASS_LIMIT=Class limit
300 General_CONFIG_CLASS_LIMIT_LONG=The maximum number of classes exceeding the Warning Limit to report.
301 General_NO_STACK_TRACE_AVAILABLE=<p><No stack trace available></p>
302 General_RULE_REQUIRES_ALL_EVENT_TYPES_ENABLED=This rule requires all of the following event types to be enabled: {0}.
303 General_RULE_REQUIRES_EVENTS_FROM_ONE_OF_MANY=This rule requires events to be available from one of the following event types: {0}.
304 General_TEXT_COULD_NOT_DETERMINE_JAVA_VERSION=The Java version could not be determined.
305 General_UNKNOWN_ADDRESS=<Unknown Address>
306 General_UNKNOWN_FILE_NAME=<Unknown File>
307 HeapContentRule_AGGR_CLASS_SCORE=Class Score
308 HeapContentRuleFactory_RULE_NAME=Heap Content
309 HeapContentRuleFactory_TEXT_INFO=Most of the heap was used by only a few classes.
310 HeapContentRuleFactory_TEXT_INFO_LONG=If the heap usage needs to be reduced, then this would be a good place to start.
311 HeapContentRuleFactory_TEXT_OK=No problems were found with the heap content.
312 HeapInspectionGcRuleFactory_RULE_NAME=GCs Caused by Heap Inspection
313 # {0} is a number
314 HeapInspectionGcRuleFactory_TEXT_INFO=The JVM performed {0} heap inspection garbage collections.
315 HeapInspectionGcRuleFactory_TEXT_INFO_LONG=Performing heap inspection garbage collections may be a problem since they usually take a lot of time.
316 HeapInspectionGcRuleFactory_TEXT_INFO_LONG_JFR=Some of these inspections were caused by the 'Object Count' JFR event. It triggers a full garbage collection at the beginning and end of every recording where that event is enabled. If recordings are only made on demand or not too often, then these garbage collections are usually not a problem since the resulting pauses are not part of the normal application behavior. If recordings are collected often, for example by automatic scripts, or if the application is sensitive to pauses, then it might become an issue. In that case you can consider disabling the 'Object Count' event.
317 HeapInspectionGcRuleFactory_TEXT_OK=The JVM did not perform any heap inspection GCs.
318 HeapInspectionGcRuleFactory_TEXT_OK_LONG=The JVM did not perform any heap inspection GCs. This is good since they usually take a lot of time.
319 HeapInspectionRule_CONFIG_WARNING_LIMIT=Heap inspection GC limit
320 HeapInspectionRule_CONFIG_WARNING_LIMIT_LONG=Warning limit ratio between number of heap inspection garbage collections and total garbage collections
321 HighGcRuleFactory_RULE_NAME=GC Pressure
322 # {0} is a time period, {1} is a time stamp, {2} is a percentage
|
282 GcPauseRatioRule_RULE_NAME=GC Pauses
283 GcPauseRatioRule_RULE_TEXT=Application efficiency was affected by GC pauses.
284 # {0} is a percentage, {1} is a timespan, {2} is a timestamp, {3} is a percentage
285 GcPauseRatioRule_RULE_TEXT_LONG=The highest ratio between garbage collection pauses and execution time was {0} % during {1} starting at {2}. The garbage collection pause ratio of the entire recording was {3} %.
286 GcPauseRatioRule_RULE_TEXT_RECOMMENDATION=Pause times may be reduced by increasing the heap size or by trying to reduce allocation.
287 GcPauseRatioRule_RULE_TEXT_OK=Application efficiency was not highly affected by GC pauses.
288
289 GcLockerRule_CONFIG_WARNING_LIMIT=GC locker ratio limit
290 GcLockerRule_CONFIG_WARNING_LIMIT_LONG=Warning limit ratio between number of garbage collections caused by GC locker and total garbage collections
291 GcLockerRule_TEXT_NA=No GC information events found.
292 GcLockerRuleFactory_RULE_NAME=GCs Caused by GC Locker
293 # {0} is a percentage
294 GcLockerRuleFactory_TEXT_INFO=The GC Locker caused {0} of the garbage collections.
295 GcLockerRuleFactory_TEXT_INFO_LONG=Garbage collections caused by the GC Locker indicates that the runtime ran a lot of JNI code. To avoid this decrease the time spent in JNI.
296 GcLockerRuleFactory_TEXT_OK=The GC Locker did not cause any garbage collections.
297 GcStallRule_RULE_NAME=GC Stall
298 GcStallRule_TEXT_OK=No indications that the garbage collector could not keep up with the workload were detected.
299 General_CONFIG_CLASS_LIMIT=Class limit
300 General_CONFIG_CLASS_LIMIT_LONG=The maximum number of classes exceeding the Warning Limit to report.
301 General_NO_STACK_TRACE_AVAILABLE=<p><No stack trace available></p>
302 General_RULE_REQUIRES_EVENTS_FROM_ONE_OF_MANY=This rule requires events to be available from one of the following event types: {0}.
303 General_TEXT_COULD_NOT_DETERMINE_JAVA_VERSION=The Java version could not be determined.
304 General_UNKNOWN_ADDRESS=<Unknown Address>
305 General_UNKNOWN_FILE_NAME=<Unknown File>
306 HeapContentRule_AGGR_CLASS_SCORE=Class Score
307 HeapContentRuleFactory_RULE_NAME=Heap Content
308 HeapContentRuleFactory_TEXT_INFO=Most of the heap was used by only a few classes.
309 HeapContentRuleFactory_TEXT_INFO_LONG=If the heap usage needs to be reduced, then this would be a good place to start.
310 HeapContentRuleFactory_TEXT_OK=No problems were found with the heap content.
311 HeapInspectionGcRuleFactory_RULE_NAME=GCs Caused by Heap Inspection
312 # {0} is a number
313 HeapInspectionGcRuleFactory_TEXT_INFO=The JVM performed {0} heap inspection garbage collections.
314 HeapInspectionGcRuleFactory_TEXT_INFO_LONG=Performing heap inspection garbage collections may be a problem since they usually take a lot of time.
315 HeapInspectionGcRuleFactory_TEXT_INFO_LONG_JFR=Some of these inspections were caused by the 'Object Count' JFR event. It triggers a full garbage collection at the beginning and end of every recording where that event is enabled. If recordings are only made on demand or not too often, then these garbage collections are usually not a problem since the resulting pauses are not part of the normal application behavior. If recordings are collected often, for example by automatic scripts, or if the application is sensitive to pauses, then it might become an issue. In that case you can consider disabling the 'Object Count' event.
316 HeapInspectionGcRuleFactory_TEXT_OK=The JVM did not perform any heap inspection GCs.
317 HeapInspectionGcRuleFactory_TEXT_OK_LONG=The JVM did not perform any heap inspection GCs. This is good since they usually take a lot of time.
318 HeapInspectionRule_CONFIG_WARNING_LIMIT=Heap inspection GC limit
319 HeapInspectionRule_CONFIG_WARNING_LIMIT_LONG=Warning limit ratio between number of heap inspection garbage collections and total garbage collections
320 HighGcRuleFactory_RULE_NAME=GC Pressure
321 # {0} is a time period, {1} is a time stamp, {2} is a percentage
|