Mongo reactive client should use Netty transport

[franz1981]

Fixes #46206

[franz1981]

@cescoffier I have no idea how SSL/TLS can interact with it

[franz1981]

@cescoffier @geoand do we want a special config to enable this?

[cescoffier]

Yes, please add a flag. I would consider being enabled by default (even if it could be seen as a breaking change).

[franz1981]

Yes, please add a flag

we want a runtime proper config option?

[geoand]

we want a runtime proper config option?

Yes please

[franz1981]

Ok I'm adding some test to the config and after speaking with @jponge I see that we always use the reactive driver so...I won't configure the Netty side with reactive only, but always

[franz1981]

I am putting it in draft, since I see that:

• non reactive uses mongo with blocking sockets
• reactive uses mongo with async sockets

And I need to understand if I can safely make to always use Netty as a transport, even in the blocking case: I am not sure of it because will likely introduce an additional thread handoff from jboss worker pool to Netty

Any idea @jponge @geoand ?

[geoand]

I have no idea how the driver works internally

[github-actions]

🎊 PR Preview 22d8b35 has been successfully built and deployed to https://quarkus-pr-main-46248-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[jponge]

Just like @geoand (aka I'm posting this to let you know that I don't know)

[franz1981]

Gotta add a test on the config @geoand but I have verified what it's written in the new config option - so I enabled Netty only in the reactive case.
I have to check what happen with tls still - since I don't see it as we test it (?)

[franz1981]

The non reactive one should just run inlined in the worker pool we provide - this by checking the mongo Java driver code + debugging it

[franz1981]

On https://www.mongodb.com/docs/drivers/java/sync/current/fundamentals/connection/tls/#customize-tls-ssl-configuration-through-the-netty-sslcontext seems that there's some work left to configure TLS/SSL or maybe it's just to switch to an alternative SSL (native) engine here - still checking

[quarkus-bot]

Status for workflow Quarkus CI

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

✅ 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.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

You can consult the Develocity build scans.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

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

✅ 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.

[franz1981]

It seems no need to do anything beyond what we already do (which is to apply SSL settings at client config level) - see https://stackoverflow.com/questions/51053679/how-to-enable-ssl-in-reactive-mongodb-client-in-spring-boot