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
For polling, retries are supported by Spring Cloud Stream framework. For streaming, retries on Pub/Sub service communication are handled by gRPC retry settings. If business logic should be retried, customers should wrap it with their own retry logic.
I still think Spring Cloud Stream documentation is somewhat incorrect, in that only polling retries are handled by the framework, while streaming retry logic is implemented directly in Kafka and Rabbit binders.
Original issue here: spring-attic/spring-cloud-gcp#2406
Duplicating the issue here for visibility.
First, confirm whether or not the Spring Cloud Stream framework handles retries for non-pollable scenario (does not seem so, see original issue).
The text was updated successfully, but these errors were encountered: