-
Notifications
You must be signed in to change notification settings - Fork 534
Introduce order for @EnableRetry #333
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Looks like there is an error in this description. The reasoning is misleading. The
RetryConfigurationadvice is not applied by any post-processors AFAIK. It is just registered as a bean to be applied later by bean-factory when it creates a proxy for a bean. And it's always applied just once, so there is no danger of creating double-proxy.@artembilan Any chance this description could be corrected? To be honest I don't know the real reason of this property to be
Ordered.LOWEST_PRECEDENCEexcept the backward compatibility. This default is actually danger as it interferes with@Transactionalannotation that is alsoOrdered.LOWEST_PRECEDENCE, so the final order is undefined. But 99% of the time you want the order to be@Retry -> @Transactionaland not vice versa because many exceptions will be thrown only at the commit phase and could be retried only by starting a new transaction.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.
Sure! We can fix that description and also make a default order as a
Ordered.LOWEST_PRECEDENCE - 1to make it working with@Transactionalas you have just explained which is really makes sense as a default behavior.I think that description was taken from the
@EnableAsyncwhich looks like does its logic slightly different than anAspectJAwareAdvisorAutoProxyCreatorinitiated by the@EnableAspectJAutoProxyfrom this@EnableRetry.Feel free to contribute the fix!
Thank you!