Artem Bilan

See one more my comment: https://github.com/spring-cloud/spring-cloud-sleuth/issues/1663#issuecomment-748202467. It looks like all the `@...Listener` abstractions suffer the same problem and the fix you propose here is not aligned with a general approach...

Superessed via https://github.com/spring-projects/spring-amqp/pull/1500

I don't think we should think about mixing responsibilities. The container is really not about declaration and registration. It is only for connecting to the specified queue and consuming messages....

Can you show, please, more stack trace to see what Spring AMQP code is involved in the problem? Any chances to have something from your what we can run on...

Well, Spring for Apache Kafka project is fully rely on the `ApplicationContext` lifecycle. So, whatever calls its `close()` would initiate the underlying `KafkaConsumer.close()`. Doesn't look like Spring adds such a...

OK. I see. Right, the `KafkaReceiver` (neither its impl) has a `close()` API, unlike `KafkaSender` does. At the same time I see that `ConsumerHandler` has one, but does not delegate...

Sorry for delay. You know we don't have nor plans, neither resources to jump into this stuff. You are always welcome with [Contribution](https://github.com/spring-projects/spring-integration-extensions/wiki/Contributor-Guidelines). This kind of new feature should go...

See https://jira.spring.io/browse/INT-3205 for more info.

Hi @mhalbritter ! I'm not sure how you use Spring Native, but all the hints are here: https://github.com/spring-projects-experimental/spring-native/blob/main/spring-native-configuration/src/main/java/org/springframework/integration/IntegrationHints.java. Probably something like `spring-native` is missed as a dependency...

OK. Something new to learn. No promises about prompt fix since it look like an API has been drastically changed... Thanks, @mhalbritter .