-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.9.1
-
Component/s: None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We want our application to start even though no replica-set seed is accessible.
Version 2.8.0 just logged an error message. Version 2.9.1 gets stuck in an infinite loop in com.mongodb.DynamicConnectionStatus.initExecutorService() printing
WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update WARNING: Server seen down: /127.0.0.1:27017 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27017] bc:java.net.ConnectException: Connection refused Sep 19, 2012 10:30:49 AM com.mongodb.ConnectionStatus$UpdatableNode update ...
The Mongo constructor never finishes.
Would it be possible to change the behavior? Or is it a feature?