Skip to content

Revise RetryTemplate for alignment with Reactor (in preparation for @Retryable) #35057

Closed
@jhoeller

Description

@jhoeller

In preparation for #34529, several characteristics of our initial RetryTemplate implementation turn out to deviate from common retry practices, as provided by Reactor's retry support which we will use side-by-side in our retry interceptor.

Most importantly, we expose the first rather than the last exception as a RetryException root cause. Also, the back-off only kicks in after a failed first retry attempt, not after the the initial exception, and does not stop on a BackOffExecution.STOP signal.

As of 7.0 M7, we consistently use BackOff and expose the last exception in RetryException now.

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions