Deprecate RetryTemplate in Listener Adapters

[garyrussell]

Functionality has been replaced by enhancements to the error handlers and causes confusion.

[Cpinto0594]

@garyrussell is it possible to add a retry mechanism for each listener? i'm registering listeners dynamically with MethodKafkaListenerEndpoint ?

[garyrussell]

Don’t ask questions on old, closed, issues. Use the Discussions tab Q&A or ask on stack overflow. Show code, configuration, and exactly what you mean.

Retry in the listener adapter has been completely replaced by functionality in the error handlers for several years, now.

[garyrussell]

If you mean you want different retry settings for listeners created by the same container factory, you can add a ContainerCustomizer to the container factory and set the retry semantics in the container's error handler there.

[pkgonan]

@garyrussell
Hi,

If the receiver adapter is changed to not retry, how do I retry?

There must be an alternative, but there seems to be no guide on how to handle it.

[artembilan]

The Javadoc of the deprecated RetryingMessageListenerAdapter says:

* @deprecated since 2.8 - use a suitably configured error handler instead.

Then according to the docs: https://docs.spring.io/spring-kafka/docs/2.8.11/reference/html/#migrating-legacy-eh and https://docs.spring.io/spring-kafka/docs/2.8.11/reference/html/#default-eh