Spring boot creates two mongo clients using spring-boot-starter-data-mongodb-reactive

[cmario]

Hi,

spring boot auto configures two MongoDB clients, one through MongoAutoConfiguration and one through MongoReactiveAutoConfiguration. If I try to exclude MongoAutoConfiguration I get the following error:

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method mongoDbFactory in org.springframework.boot.autoconfigure.data.mongo.MongoDataAutoConfiguration required a bean of type 'com.mongodb.MongoClient' that could not be found.
	- Bean method 'mongo' not loaded because auto-configuration 'MongoAutoConfiguration' was excluded

Then, If I try to exclude MongoDataAutoConfiguration as well I get the following error:

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 1 of method reactiveMongoTemplate in org.springframework.boot.autoconfigure.data.mongo.MongoReactiveDataAutoConfiguration required a bean of type 'org.springframework.data.mongodb.core.convert.MongoConverter' that could not be found.
	- Bean method 'mappingMongoConverter' not loaded because auto-configuration 'MongoDataAutoConfiguration' was excluded

Looks that is not possible to exclude the non reactive part.
Below you can find a simple example where "Cluster created with settings....etc" is logged two times:
https://github.com/cmario/spring-boot-embedded-mongodb

Regards
Mario

[wilkinsona]

Is this causing you a problem beyond the logging that you've noticed? The two clients that are auto-configured are not the same. One is an instance of com.mongodb.reactivestreams.client.MongoClient and the other is an instance of com.mongodb.MongoClient.

[cmario]

Actually I had a weird behaviour in my application. Is totally random and happened to me 2/3 times that a RESTFul endpoint with just one query to MongoDB, it just stuck. The connection time and the socket time as per the connection string wasn't respected, no errors and no logs. The connection pool was looking fine because I was able to see in the logs that the idle connections were closed and reopened. Restarting mongodb itself didn't help, I had to restart the application itself.
That is the reason I started to look into it and I realized the two mongodb clients were created. Of course I'm not sure that the two things are related and I know that we are talking about two different clients, but you know, less stuff you have less stuff can be broken :-).
Unfortunately is quite random and not easy do debug. I put in debug mode the mongodb package, at least I hope to see something next time that happens. I will update you.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.