Motivation:
There's an issue when logging the current connection inside R2dbcTransactionManager#doBegin :
the mono object is logged instead of the connection lambda parameter, resulting in wrong log
ex)
2023-01-11 15:09:32.809 DEBUG 45809 --- [actor-tcp-nio-2] o.s.r.c.R2dbcTransactionManager : Acquired Connection [MonoRetry] for R2DBC transaction
Comment From: pivotal-cla
@j-min5u Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@j-min5u Thank you for signing the Contributor License Agreement!
Comment From: simonbasle
mmh looks like there's an issue with the backport bot. considering that, and the fact the 6.0.4 and 5.3.25 releases are planned for today, I won't rush things and instead reassign this to 6.0.5 and defer merging.
Comment From: simonbasle
TODO
- [x] add the for: backport-to-5.3.x and perform the backport once 6.0.4 is out the door