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

The driver does not start if the replica set is not available

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.9.1
    • None
    • None

    Description

      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?

      Attachments

        Activity

          People

            Unassigned Unassigned
            dart0 Lukas Krecan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: