How to capture error messages during binder creation/initialization
Using Spring Boot 3.3.6 and Spring Cloud 2023.0.3, this minimal code works great for consuming messages from a Kafka topic:
How to capture error messages during binder creation/initialization
Using Spring Boot 3.3.6 and Spring Cloud 2023.0.3, this minimal code works great for consuming messages from a Kafka topic:
How to capture error messages during binder creation/initialization
Using Spring Boot 3.3.6 and Spring Cloud 2023.0.3, this minimal code works great for consuming messages from a Kafka topic:
How to start Spring-Cloud-Stream consumer bindings programmatically on application “readiness”?
I’m working on an application where I need to programmatically start the processing of messages. The application uses Spring Cloud Stream with two different binder implementations: one from Solace and another custom implementation of the Spring Cloud Stream binder based on TIBCO Rendezvous.
Exception encountered after upgrading Spring Cloud Stream Schema Registry Server from version 4.1.2 to 4.1.3
After upgrading to org.springframework.cloud:spring-cloud-stream-schema-registry-server:4.1.3, we are receiving the following stack trace in code that works fine with version 4.1.2:
Is “spring.cloud.stream.dynamicDestinations” still a valid configuration option?
I’m using spring-cloud-stream 4.1.1 and trying to set the configuration option spring.cloud.stream.dynamicDestinations, but it doesn’t seem to be having the desired effect (or I’m not understanding how it’s supposed to be used).
Using stream bridge to send message from one onsumer to another consumer
I had seen issue – StreamBridge not sending acknowledgment header and corresponding code as below for GH–2563.