Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-907

cursor not found on server

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.2
    • Component/s: Connection Management
    • None
    • Environment:
      Mongo version :2.2.3
      Num of object is a 47110.
      Driver mongodb is a 2.9.3
      Pentaho PDI: 4.4.0

      Jul 31, 2013 10:34:37 AM com.mongodb.DBPortPool gotError
      WARNING: emptying DBPortPool to ec2-54-216-117-46.eu-west-1.compute.amazonaws.com/10.208.48.102:27017 b/c of error
      java.net.SocketException: Connection 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:46)
      at org.bson.io.Bits.readFully(Bits.java:33)
      at org.bson.io.Bits.readFully(Bits.java:28)
      at com.mongodb.Response.<init>(Response.java:40)
      at com.mongodb.DBPort.go(DBPort.java:124)
      at com.mongodb.DBPort.call(DBPort.java:74)
      at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:283)
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:256)
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:225)
      at com.mongodb.DBApiLayer$Result._advance(DBApiLayer.java:431)
      at com.mongodb.DBApiLayer$Result.hasNext(DBApiLayer.java:400)
      at com.mongodb.DBCursor._hasNext(DBCursor.java:464)
      at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
      at org.pentaho.di.trans.steps.mongodbinput.MongoDbInput.processRow(MongoDbInput.java:77)
      at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50)
      at java.lang.Thread.run(Thread.java:662)
      ERROR 31-07 10:34:37,118 - Data - Unexpected error
      ERROR 31-07 10:34:37,120 - Data - com.mongodb.MongoException$Network: can't call something : ec2-54-216-117-46.eu-west-1.compute.amazonaws.com/10.208.48.102:27017/ETL
      at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:292)
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:256)
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:225)
      at com.mongodb.DBApiLayer$Result._advance(DBApiLayer.java:431)
      at com.mongodb.DBApiLayer$Result.hasNext(DBApiLayer.java:400)
      at com.mongodb.DBCursor._hasNext(DBCursor.java:464)
      at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
      at org.pentaho.di.trans.steps.mongodbinput.MongoDbInput.processRow(MongoDbInput.java:77)
      at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: java.net.SocketException: Connection 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:46)
      at org.bson.io.Bits.readFully(Bits.java:33)
      at org.bson.io.Bits.readFully(Bits.java:28)
      at com.mongodb.Response.<init>(Response.java:40)
      at com.mongodb.DBPort.go(DBPort.java:124)
      at com.mongodb.DBPort.call(DBPort.java:74)
      at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:283)
      ... 9 more

            Assignee:
            Unassigned Unassigned
            Reporter:
            sowe Rafael Valenzuela
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: