-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Fix R2dbcTransactionManager debug log: don't log a Mono #29800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix R2dbcTransactionManager debug log: don't log a Mono #29800
Conversation
@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. |
@j-min5u Thank you for signing the Contributor License Agreement! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the contribution @j-min5u !
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. |
TODO
|
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