Exception in monitor thread while connecting to server localhost:27017 while accessing MongoDB with Java

Question

I have the following exception when running Java app for MongoDB:

[localhost:27017] org.mongodb.driver.cluster : Exception in monitor thread while connecting to server localhost:27017 while accessing MongoDB with Java

Call stack is follows:

com.mongodb.MongoSocketOpenException: Exception opening socket
    at com.mongodb.connection.SocketStream.open(SocketStream.java:63) ~[mongodb-driver-core-3.0.4.jar:na]
    at com.mongodb.connection.InternalStreamConnection.open(InternalStreamConnection.java:114) ~[mongodb-driver-core-3.0.4.jar:na]
    at com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:127) ~[mongodb-driver-core-3.0.4.jar:na]
    at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]
Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) ~[na:1.8.0_45]
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) ~[na:1.8.0_45]
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) ~[na:1.8.0_45]
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_45]
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_45]
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) ~[na:1.8.0_45]
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_45]
    at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_45]
    at com.mongodb.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:50) ~[mongodb-driver-core-3.0.4.jar:na]
    at com.mongodb.connection.SocketStream.open(SocketStream.java:58) ~[mongodb-driver-core-3.0.4.jar:na]
    ... 3 common frames omitted

Neither of these names belong to my application. Also I have NO MONGODB server on local host. I am using remote host and setting it later. An exception occurs BEFORE any of my statements concerning Mongo.

UPDATE

This is probably some Spring provided beans accessing Mongo. How to disable them?

My config contains following dependencies:

dependencies {
    compile('javax.media:jai_core:1.1.3')
    //compile('jai_core:1.1.3')

//  compile('org.springframework.boot:spring-boot-starter-data-mongodb')
    compile('org.mongodb:mongodb-driver:3.0.4')
    compile('org.mongodb:bson:3.0.4')

    compile('org.geotools:gt-api:14.2')
    compile('org.geotools:gt-shapefile:14.2')
    compile('org.geotools:gt-geometry:14.2')
    compile('org.geotools:gt-referencing:14.2')
    compile('org.geotools:gt-geojson:14.2')
    compile('org.geotools:gt-mongodb:14.2')

    compile('org.springframework.boot:spring-boot-starter-web')
    providedRuntime('org.springframework.boot:spring-boot-starter-tomcat')
    testCompile('org.springframework.boot:spring-boot-starter-test') 
}

i.e. I have removed org.springframework.boot:spring-boot-starter-data-mongodb and was thinking will use Mongo myself...

UPDATE2

I found related question: How to disable spring-data-mongodb autoconfiguration in spring-boot

score 68 · Accepted Answer · answered Feb 15 '16 at 18:05

68

I was to add exclusion annotation to my main annotated class,

i.e. instead of

@SpringBootApplication

I should have

@SpringBootApplication
@EnableAutoConfiguration(exclude={MongoAutoConfiguration.class})

answered Feb 15 '16 at 18:05

Dims

47,675
117
331
600

1

you are god, bro. – funky-nd May 22 '18 at 15:53
Martin check this [post](https://stackoverflow.com/questions/46281830/i-cant-exclude-mongoautoconfiguration-in-springboot-kotlin-mongosocketopenexce) – LuCG Apr 07 '19 at 21:25
1

if above method is not working, you can try this https://stackoverflow.com/a/34415014/5300484 – Sachith.Wanni Oct 30 '19 at 06:19
1

@Dims what does `@EnableAutoConfiguration(exclude={MongoAutoConfiguration.class})` do? – vanya May 04 '22 at 11:51
1

@Dims as of today it should be `@SpringBootApplication(exclude={MongoAutoConfiguration.class})` – Steffen Ebert Feb 04 '23 at 16:50

score 8 · Answer 2 · edited Jan 19 '20 at 23:29

8

Try adding

spring.data.mongodb.host=hostIpOnWhichMongoIsRunning
spring.data.mongodb.port=27017

into application.properties.

If Mongo is not running on localhost, this should fix the issue.

edited Jan 19 '20 at 23:29

pinckerman

4,115
6
33
42

answered Mar 28 '18 at 08:16

Vaibhav

103
1
7

Had a similar issue, setting these properties solved my problem, Thanks !!! – Elazar Neeman Oct 22 '19 at 09:00

score 6 · Answer 3 · answered Jul 23 '21 at 04:18

6

My IDEA suggested that I do this.

@SpringBootApplication(exclude = {MongoAutoConfiguration.class})

answered Jul 23 '21 at 04:18

aszswaz

609
3
10

score 2 · Answer 4 · answered Dec 24 '21 at 19:09

2

In my case the mistake was not to have authorized my development environment. So I allowed connections from any IP (not a good idea for prod env) by adding the rule 0.0.0.0/0. You add this rule from the Network Access section from the atlas dashboard.

answered Dec 24 '21 at 19:09

Saliou673

209
2
10

to add to this, had to switch my network due to which the IP address got changed. check if your IP address is added for your MongoDB cluster. (Adding 0.0.0.0/0 will also do.) – kaustubhd9 Mar 18 '23 at 12:28

score 1 · Answer 5 · edited May 27 '19 at 09:50

I can't say for sure. It's kind of not enough information question.

I can say that: Mongo driver by default tries to connect to the local host. Probably you haven't specified the Mongo host/port.

So you'll have to configure the MongoDB host/port/credentials (if you have those).

Maybe it's network related issue or firewall (try to connect to MongoDB from your machine directly with cli / even running a basic program that uses only mongo driver).

From the stacktrace I don't see any usage of Spring, so more information is required to say for sure.

In general you can analyze the dependencies in Gradle by using gradle dependencies command (see here).

score 0 · Answer 6 · answered Apr 09 '21 at 15:54

0

I had the same exception when trying to connect MongoDB with spring-boot. In my case, I forgot to add the @Configuration annotation in the MongoDB Configuration class I created.

After adding this it worked for me.

answered Apr 09 '21 at 15:54

Pulsara Sandeepa

915
10
25

score 0 · Answer 7 · edited Jun 23 '21 at 08:26

0

I changed the scope(It was Test before)

<dependency>
<groupId>de.flapdoodle.embed</groupId>
<artifactId>de.flapdoodle.embed.mongo</artifactId>
<scope>4.2.3</scope>
</dependency>

edited Jun 23 '21 at 08:26

Slava Rozhnev

9,510
6
23
39

answered Jun 23 '21 at 07:23

Anisha

1

score 0 · Answer 8 · answered Jun 01 '22 at 11:03

0

In my case mongoDB internal port was not mapped to external. Using command docker run -p 27017:27017 -d mongo resolved my issue.

answered Jun 01 '22 at 11:03

Shashi Ranjan

87
1
10

score 0 · Answer 9 · answered Dec 13 '22 at 03:43

0

check your mongo with cmd "mongo" if mongo is deathed follow step 1: open search windown 2: search "services" 3: find MongoDB Service and right click then click start on popup

answered Dec 13 '22 at 03:43

Đào Tuyên

51
4

score -3 · Answer 10 · answered Feb 15 '16 at 17:36

-3

It seems your server is not running. Also if it running, it is doing so on a different port.

answered Feb 15 '16 at 17:36

rootExplorr

575
3
17

My server is running, but not on `localhost` – Dims Feb 15 '16 at 17:39
1

Check your address then. – rootExplorr Feb 15 '16 at 17:40
I checked. It is not `localhost`. – Dims Feb 15 '16 at 17:41
Try printing out the address. As per the error trace the code is reaching out to localhost. – rootExplorr Feb 15 '16 at 17:41

Exception in monitor thread while connecting to server localhost:27017 while accessing MongoDB with Java

10 Answers10

Linked