PollingEngine::poll(): error polling emc-smarts : (conf/smarts-pm.xml) java.net.SocketTimeoutException: Read timed out

Products

• VMware Smart Assurance

Issue/Introduction

Read time out exceptions are seen in the Smarts Collector log file. This impacts and degrades the performance of the Smarts Collector. 

WARNING -- [2014-02-19 09:18:50 IST] -- PollingEngine::poll(): error polling emc-smarts : <APM_Domain> (conf/smarts-pm.xml)
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at com.smarts.remote.SmRemoteDomainManager$BetterBufferedInputStream.read(SmRemoteDomainManager.java:594)
at java.io.FilterInputStream.read(FilterInputStream.java:66)
at java.io.DataInputStream.readByte(DataInputStream.java:248)
at com.smarts.remote.SmRemoteInputStream.readDmByte(SmRemoteInputStream.java:58)
at com.smarts.remote.SmRemoteInterfaceHandler.getResponse(SmRemoteInterfaceHandler.java:121)
at com.smarts.remote.SmRemoteInterfaceHandler.getProperties(SmRemoteInterfaceHandler.java:4367)
at com.smarts.remote.SmRemoteInterfaceHandler.getProperties(SmRemoteInterfaceHandler.java:4349)
at com.watch4net.apg.v2.collector.plugins.smarts.SmTopologyManager.getProperties(SmTopologyManager.java:614)
at com.watch4net.apg.v2.collector.plugins.polling.FetchClassInstanceTask.compute(FetchClassInstanceTask.java:46)
at com.watch4net.async.EvaluatorTask.run(EvaluatorTask.java:104)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:662)

Environment

Watch4Net/MnR - 7.x

Smarts - 10.1.x

Resolution

Such errors indicate that the Smarts domain is not able to respond to the polling request.

This could be due to high CPU utilization on the Smarts domain host machine. The error messages are originating from the Smart IP domains and not from Watch4Net/M&R. Please review the Smarts IP domain logs for additional troubleshooting.