jchrys

@radovanradic, thank you for your patience. The issue has been resolved in `io.asyncer:r2dbc-mysql:1.1.2`.

@nkonev Thank you for sharing your findings! I would suggest using `io:asycner:r2dbc-mysql:1.0.0` instead of `dev.miku:r2dbc-mysql` since the latter is out of date and inactive for a long time. The `io:asyncer:2dbc-mysql`...

Thanks @mirromutth for pinning this issue. 😄

🎉We've just released the v`1.0.2` of `r2dbc-mysql`. (v`0.9.3` for r2dbc-spi:0.9.1.RELEASE as well) This version fully supports the latest `r2dbc-spi`, providing improved performance and stability. Please check out our repository: https://github.com/asyncer-io/r2dbc-mysql

`MySqlConnectionConfiguration.builder()` returns the builder instance. please check if you have configured your dependencies correctly.

Hello, @xuantungmta. Please use `asyncer.io:r2dbc-mysql:1.0.0` that includes the changes mentioned by @wgdetective. it is successor to `mirromuth's r2dbc-mysql`.

Which version of r2dbc-spi are you using? could you try to replace `dev.miku.r2dbc-mysql` with `io.asyncer:r2dbc-mysql:0.9.1` and see if error is still there?

The issue arises because MySQL server disconnects your connection due to the wait_timeout setting. To address this, set your connection pool's` max idle timeout` < `wait_timeout` value.

I think we could help you further, If you could share us minimum reproducible steps. Please ensure that you are returning your connection to the pool correctly. I suggest escalating...

Hello, @tabdelbari. Thank you for bringing this feature request to our attention. I'll be taking up the task to work on implementing multiple host configurations. Considering that the R2DBC SPI...