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 Daniel Gottlieb, 1 year ago
Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=REPLICA_SET, servers=[{address=scrubbedProblemHost:scrubbedPort, type=UNKNOWN, state=CONNECTING}, {address=scrubbedArbiter
via Stack Overflow by Michael Dussere
, 1 year ago
Timed out after 30000 ms while waiting for a server that matches PrimaryServerSelector. Client view of cluster state is {type=REPLICA_SET, servers=[{address=XX.XXX.109.38:26016, type=REPLICA_SET_SECONDARY, roundTripTime=0.5 ms, state=CONNECTED}]
via GitHub by MercusChan
, 2 months ago
Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=UNKNOWN, servers=[{address=172.17.0.1:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.SocketTimeoutException: connect timed out}}]
via Stack Overflow by caroline
, 1 week ago
Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=UNKNOWN, servers=[{address=mongodb://<dbuser>:<dbpassword>@ds237489.mlab.com:37489/mynosqlproject:27017, type=UNKNOWN
via Stack Overflow by RafiChozhan
, 2 years ago
Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=UNKNOWN, servers=[{address=ds019468.mlab.com:19468, type=UNKNOWN, state=CONNECTING, exception
via Stack Overflow by jinshui
, 1 year ago
Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=REPLICA_SET, servers=[{address=172.31.11.73:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.SocketTimeoutException: connect timed out}}]
com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=REPLICA_SET, servers=[{address=scrubbedProblemHost:scrubbedPort, type=UNKNOWN, state=CONNECTING}, {address=scrubbedArbiter, type=REPLICA_SET_ARBITER, roundTripTime=7.8 ms, state=CONNECTED}, {address=scrubbedWorkingHost, type=REPLICA_SET_SECONDARY, roundTripTime=1.0 ms, state=CONNECTED}, {address=scrubbedWorkingHost, type=REPLICA_SET_SECONDARY, roundTripTime=0.9 ms, state=CONNECTED}]	at com.mongodb.connection.BaseCluster.createTimeoutException(BaseCluster.java:369)	at com.mongodb.connection.BaseCluster.selectServer(BaseCluster.java:101)	at com.mongodb.binding.ClusterBinding$ClusterBindingConnectionSource.(ClusterBinding.java:75)	at com.mongodb.binding.ClusterBinding$ClusterBindingConnectionSource.(ClusterBinding.java:71)	at com.mongodb.binding.ClusterBinding.getWriteConnectionSource(ClusterBinding.java:68)	at com.mongodb.operation.OperationHelper.withConnection(OperationHelper.java:219)	at com.mongodb.operation.CreateIndexesOperation.execute(CreateIndexesOperation.java:111)	at com.mongodb.operation.CreateIndexesOperation.execute(CreateIndexesOperation.java:66)	at com.mongodb.Mongo.execute(Mongo.java:781)	at com.mongodb.Mongo$2.execute(Mongo.java:764)	at com.mongodb.DBCollection.createIndex(DBCollection.java:1541)