🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Retry mechanism with delay

We are adapting our services to use Solace, and one of our applications uses a retry mechanism with delay from RabbitMQ in which an error message would be sent to a DLQ, which had a TTL configuration and, after the TTL expiration, it would be sent back to the initial queue. Beyond that, the message had a specific header parameter that specified the retry number (x-death). After some retries, we could give up end send an error message to the end user. This could be achieved with the following configuration:

[...]
spring.cloud.stream.bindings.queueName.consumer.max-attempts=1
spring.cloud.stream.rabbit.bindings.queueName.consumer.auto-bind-dlq=true
spring.cloud.stream.rabbit.bindings.queueName.consumer.dlq-ttl=1000
spring.cloud.stream.rabbit.bindings.queueName.consumer.dlq-dead-letter-exchange=

Is there a similar way to do this in Solace?

Answers