Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via JIRA by Leif Mortenson, 1 year ago
couldn't connect to [io/192.168.0.10:27017] bc:java.net.ConnectException: Operation timed out
via JIRA by Leif Mortenson, 1 year ago
couldn't connect to [io/192.168.0.10:27017] bc:java.net.ConnectException: Operation timed out
via JIRA by Joseph Wang, 1 year ago
couldn't connect to [ip-10-166-59-166/10.166.59.166:20000] bc:java.net.ConnectException: Connection refused
via Stack Overflow by Jason
, 2 years ago
couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused: connect
via Stack Overflow by KumMas
, 2 years ago
couldn't connect to [/192.168.80.128:27017] bc:java.net.ConnectException: Connection refused: connect
via GitHub by knuthaug
, 1 year ago
couldn't connect to [nikopol.apress.local/32.10.8.124:27017] bc:java.net.ConnectException: Connection refused
java.io.IOException: couldn't connect to [io/192.168.0.10:27017] bc:java.net.ConnectException: Operation timed out	at com.mongodb.DBPort._open(DBPort.java:205)	at com.mongodb.DBPort.go(DBPort.java:94)	at com.mongodb.DBPort.go(DBPort.java:75)	at com.mongodb.DBPort.call(DBPort.java:65)	at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:215)	at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:295)	at com.mongodb.DBCursor._check(DBCursor.java:354)	at com.mongodb.DBCursor._hasNext(DBCursor.java:484)	at com.mongodb.DBCursor.hasNext(DBCursor.java:509)	at com.mongodb.jdbc.MongoResultSet.next(MongoResultSet.java:640)