The quarkus.mongodb.socket-timeout configuration property was previously ignored. We fixed that and in passing, we renamed it to quarkus.mongodb.read-timeout to be more accurate.

If you used it, you will now get a warning about having an unapplied property but the behavior will be the same as before i.e. the property not being applied. If you want to configure it, just replace the old name with the new one.