Retour
-
Titre
The NMS agent gathers data for a short while and then stops collecting data. -
Description
The NMS agent gathers data for a short while and then stops.Initially the NMS agent log contained "OutOfMemory" errors.The FglAM JVM heap was incrementally increased to 4GB.After increasing the JVM heap to 4GB the NMS agent stopped collecting data but instead of reporting "OutOfMemory" errors the agent log contained "InvocationTargetException" error messages..Following is an example of the "InvocationTargetException" error messages being seen:2014-06-18 13:11:37.259 ECHO <NMSAgent/5.6.4.3/NMSAgent/NMSAgent_on_host.domain.com> ERROR [Quartz-31] com.quest.glue.core.agent.scheduler.CollectorCallback - An unexpected error occurred which may cause undesired behavior. You may want to contact Quest Software customer support if you see this error again: An error occurred while invoking collection method collectFlowTopN on ScheduleTask Group NMSAgent/5.6.4.3/NMSAgent/NMSAgent_on_host.domain.com-Collectorjava.lang.reflect.InvocationTargetException...Caused by: java.util.concurrent.TimeoutException: Failed to acquire the READ lock for agent NMSAgent/5.6.4.3/NMSAgent/NMSAgent_on_host.domain.com because it is being held by another thread(s). One of more of those threads could be hung or deadlocked.... -
Cause
The "InvocationTargetException"errors mean that the collections are taking much longer than the collection interval so the agent is not able to obtain a new lock to perform the next collection because one is already in progress. More JVM heap was being used than would normally be used because a large number of samples would be held in memory before being sent to the FMS. -
Résolution
Increase the collection intervals. Start by doubling the collection intervals.To increase the collection intervals:1). Navigate to the Agent Status page (Administration | Agents | Agent Status).2). Highlight the NMS agent, click the "Edit Properties", button and then click the "Modify the private properties for this agent" link.3). Clone the "Collector Config" list under the "Data Collection Scheduler" section and give the cloned list a new name.4). Double the metrics and alertData values in the "Default Collection" column.5). If the flowMetrics, flowTopN, and agentLoad values are less than 60 increase them to 60.6). Save the changes.