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
Resolvesspring-projects#1455
Add an advice chain to the stream listener container and its factory.
Add a `StreamMessageRecoverer` for native stream messages.
Add a retry interceptor to work with native stream messages.
**cherry-pick to 2.4.x**
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Apr 26, 2022
Resolvesspring-projects#1455
Add an advice chain to the stream listener container and its factory.
Add a `StreamMessageRecoverer` for native stream messages.
Add a retry interceptor to work with native stream messages.
**cherry-pick to 2.4.x**
Resolves#1455
Add an advice chain to the stream listener container and its factory.
Add a `StreamMessageRecoverer` for native stream messages.
Add a retry interceptor to work with native stream messages.
**cherry-pick to 2.4.x**
* Add since to new setter.
Resolves#1455
Add an advice chain to the stream listener container and its factory.
Add a `StreamMessageRecoverer` for native stream messages.
Add a retry interceptor to work with native stream messages.
**cherry-pick to 2.4.x**
* Add since to new setter.
Expected Behavior
I spotted this when looking into this: Can StreamRabbitListenerContainerFactory message listeners retry messages?
Retries for deliveries in the classic listener containers is implemented using the advice chain (with a retry interceptor https://docs.spring.io/spring-amqp/docs/current/reference/html/#retry).
So there's no standard way to handle retries as part of the stream container factory, that do exist on the SimpleMessageListenerContainer
Current Behavior
There is currently no advice chain support in the StreamListenerContainer.
Context
There are workarounds - suggested in the Can StreamRabbitListenerContainerFactory message listeners retry messages? - but it pushes the retry logic out into all the
@RabbitListener
s, instead of keeping it central.The text was updated successfully, but these errors were encountered: