Application fails to reconnect with DB after connection closed about r2dbc-mysql HOT 4 CLOSED

@ssharan27
After reviewing the issue, it appears that the problem lies with the connection pool rather than the driver. In HikariCP, when acquiring a connection, it attempts to retrieve it repeatedly within the maxAcquireTime, even if the connection is closed. On the other hand, r2dbc-pool seems to attempt a limited number of retries, specified by maxRetry.

To prevent the r2dbc connection pool from retrieving closed connections due to remote mysql server, I found that setting the maxIdleTime to a value lower than the wait_timeout of MySQL resolves the issue. This adjustment ensures that such occurrences no longer happen.

logging.level.org.springframework.r2dbc=DEBUG
spring.r2dbc.url=r2dbc:mysql://localhost:3306/test
spring.r2dbc.username=root
spring.r2dbc.password=password
spring.r2dbc.pool.max-idle-time=10s <-- added

if you believe there is a need to modify the current behavior of the connection pool, I recommend creating an issue on the following GitHub repository: https://github.com/r2dbc/r2dbc-pool. They will be better equipped to assist you with the necessary modifications.

Thanks a lot for your understanding and cooperation. 👍

from r2dbc-mysql.

Thanks @jchrys and @JohnNiang for taking a look, will raise this on r2dbc pool repo. In the mean time will tweak the maxIdleTime value. Cheers 👍

from r2dbc-mysql.

@ssharan27 Thank you for submitting a high-quality issue report for r2dbc-mysql!
Your detailed input is greatly appreciated and will help us investigate and resolve the problem effectively.
We value your contribution to improving the project and will keep you updated on our progress.

Thanks again!

from r2dbc-mysql.

Closed this issue
cc @JohnNiang @ssharan27

from r2dbc-mysql.