Docs enhancement: Add warning about multiple Reactive Mongodb Clients

[MaciejDromin]

I was trying to create multiple reactive MongoDB clients using following configuration property:

quarkus.mongodb.client1.connection-string=mongodb://localhost:27017/db1
quarkus.mongodb.client2.connection-string=mongodb://localhost:27017/db2

And then using them two different Entities:

@MongoEntity(clientName = "client1")
...
@MongoEntity(clientName = "client2")

I quickly found out that it is not possible but couldn't find anything in the docs about it. To avoid confusion I propose this doc enhancement.

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit bd43d15.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[geoand]

This seems odd to me as I don't remember any specific reason why what you tried originally would not work.
Do you have a sample application that shows the problem in action?

[MaciejDromin]

This seems odd to me as I don't remember any specific reason why what you tried originally would not work. Do you have a sample application that shows the problem in action?

Sure, I will try to create a small reproducer later today

[MaciejDromin]

@geoand You were right, it was my bad I was trying to inject regular client which obviously didn't work. But when I was creating the reproducer I confirmed other issue. When trying to use two different reactive clients, quarkus is always creating ryuk and mongodb containers even tho I have a running mongo on default port. What's odd is, it is not even using it.


There is no such issue when running a single client.


Here is the reproducer:
https://github.com/MaciejDromin/mongo-quarkus-issue
https://github.com/MaciejDromin/mongo-quarkus-issue/tree/single-client

[geoand]

@MaciejDromin thanks for finding that! Unfortunately fixing this requires is a bit tricky and I've opened #45388 to track it.