exception mongo driver

[nyc]

Dear All,

My production server has mongo 2.0.5 install and following is the exception quite frequently
so please help resolving this concern

: com.mongodb.MongoException$Network: can't call something
        at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:211)
        at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:303)
        at com.mongodb.DBCursor._check(DBCursor.java:360)
        at com.mongodb.DBCursor._hasNext(DBCursor.java:490)
        at com.mongodb.DBCursor.hasNext(DBCursor.java:515)
   
Caused by: 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.read1(BufferedInputStream.java:258)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
        at org.bson.io.Bits.readFully(Bits.java:35)
        at org.bson.io.Bits.readFully(Bits.java:28)
        at com.mongodb.Response.<init>(Response.java:39)
        at com.mongodb.DBPort.go(DBPort.java:123)
        at com.mongodb.DBPort.go(DBPort.java:82)
        at com.mongodb.DBPort.call(DBPort.java:72)
        at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:202)

[Moacy Barros]

Hello nyc,

try to telnet/ssh your server from some possible sources to be sure there is no network related issues.

Please, provide mongod start up command line and client access configurations you are using, maybe you are running many clients against the same mongod instance? There are some occurrence of this kind of exception due the use of wrong port number on client side.

Regards,

Moacy