-
-
Notifications
You must be signed in to change notification settings - Fork 489
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
[FP] TransactionManager improvements #6052
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Jody Garnett <[email protected]> Co-authored-by: cmangeat
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 Jose this looks good, also confirmed TransactionAspectDoRunInTransactionTest does not change at all (as the API contract has not changed with these improvements).
if ( status == null || status.isCompleted()){ | ||
// not calling return here to preserve previous logic | ||
// we can check if the following log messages are seen before taking defensive action | ||
Log.debug( Log.JEEVES,"transactionManager.commit called unexpectedly when transaction is already completed "); |
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.
I did not want to be agressive with calling out invalid state like this while doing improvements, since this is on master we could change this to a warning or even failure.
|
Co-authored-by: Jody Garnett [email protected]
Co-authored-by: cmangeat
Related to #5308 committed to 3.12.x branch