Add BackOffExecution to isolate state
This commit separates the BackOff configuration from an actual execution. BackOffExecution now contains all the state of a particular execution and BackOff is only meant to start (i.e. create) a new execution. The method "reset" has been removed as its no longer necessary: when an execution does not need to be used for a given operation anymore it can be simply discarded. Issue: SPR-11746
This commit is contained in:
@@ -41433,10 +41433,10 @@ choices and message redelivery scenarios.
|
||||
|
||||
| back-off
|
||||
| Specify the `BackOff` instance to use to compute the interval between recovery
|
||||
attempts. If the `BackOff` implementation returns `BackOff#STOP`, the listener
|
||||
container will not further attempt to recover. The `recovery-interval value is
|
||||
is ignored when this property is set. The default is a `FixedBackOff` with an
|
||||
interval of 5000 ms, that is 5 seconds.
|
||||
attempts. If the `BackOffExecution` implementation returns `BackOffExecution#STOP`,
|
||||
the listener container will not further attempt to recover. The `recovery-interval
|
||||
value is ignored when this property is set. The default is a `FixedBackOff` with
|
||||
an interval of 5000 ms, that is 5 seconds.
|
||||
|
||||
| recovery-interval
|
||||
| Specify the interval between recovery attempts, in milliseconds. Convenience
|
||||
|
||||
Reference in New Issue
Block a user