You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
generateFromSleepingBackOffPolicy method in org.springframework.kafka.retrytopic.BackOffValuesGenerator
I have removed the code to set the maxBackOffPeriod, if the BackOffPolicy is UniformRandomBackOffPolicy. This is not required since, when sleeper is added to the UniformRandomBackOffPolicymaxBackOffPeriod is not modified. This could be an issue with the earlier versions of spring-retry. But, latest version of spring-kafka 3.3 and spring-retry 2.0.8, this is not an issue.
Modify addIfAbsent in org.springframework.kafka.retrytopic.ListenerContainerFactoryResolver.Cache to use putIfAbsent, rather than explictly checking for the key, if it is not there than adding it to the HashMap.
Please give your comments.
The text was updated successfully, but these errors were encountered:
Following code could be considered to refactor.
generateFromSleepingBackOffPolicy
method inorg.springframework.kafka.retrytopic.BackOffValuesGenerator
I have removed the code to set the
maxBackOffPeriod
, if the BackOffPolicy isUniformRandomBackOffPolicy
. This is not required since, when sleeper is added to theUniformRandomBackOffPolicy
maxBackOffPeriod
is not modified. This could be an issue with the earlier versions of spring-retry. But, latest version of spring-kafka 3.3 and spring-retry 2.0.8, this is not an issue.Modify
addIfAbsent
inorg.springframework.kafka.retrytopic.ListenerContainerFactoryResolver.Cache
to useputIfAbsent
, rather than explictly checking for the key, if it is not there than adding it to the HashMap.Please give your comments.
The text was updated successfully, but these errors were encountered: