Artem Bilan

I think the problem is in the `AbstractMessageChannelBinder` where we register an error channel bean: ``` String errorChannelName = errorsBaseName(destination, group, consumerProperties); ... protected String errorsBaseName(ConsumerDestination destination, String group, C...

I would say such a timeout exception has to be retriable. But doesn't look like we have any options for the producer binding to apply it...

Just FYI the `GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:190)` does the `MessageChannel.send()` exactly. The `ChannelInterceptor` is a part of the `MessageChannel` already. So, the `send` you see in the stack trace is misleading you a...

May be this one can help you somehow: https://docs.spring.io/spring-integration/docs/current/reference/html/messaging-endpoints.html#idempotent-receiver ? The point is that `MessageChannel` indeed returns `false` when no message after `preSend()`: ``` message = interceptorList.preSend(message, this, interceptorStack); if...

I think the plan is to implement Spring Integration Channel Adapters for Redis Streams first of all: https://github.com/spring-projects/spring-integration/issues/3226. With that on board I don't think that old Redis Binder code...

We can't do that until we will be able to upgrade to AWS SDK v2 the whole stack: https://github.com/spring-projects/spring-integration-aws/issues/155

That's right, but this "push" issue is going to be reconsidered only when we will have upgraded already to AWS SDK v2... See all those linked issues.

@paparaju , we cannot do anything here until this one: https://github.com/spring-projects/spring-integration-aws/issues/155. I don’t expect too much changes in our interfaces: only new dependencies and some new options. And probably new...

Throwing `TimeoutException` means exposing an internal API which is not a goal of this "send-n-receive" protocol. No one pursued consistency with `Future.get()` over here. That's just a decision to make...

> I would suggest putting it straight in javadoc. Sure! Feel free to contribute such a fix: https://github.com/spring-projects/spring-amqp/blob/main/CONTRIBUTING.adoc !