Detail on when messages are redelivered to a client can be found in the Message Redelivery and DLQ Handling section. You can configure the RedeliveryPolicy on your ActiveMQConnectionFactory or ActiveMQConnection to customize exactly how you want the redelivery to work.
You can use Java code, Spring or the Connection Configuration URI to customize this.
The back-off multiplier.
The percentage of range of collision avoidance if enabled.
The initial redelivery delay in milliseconds.
Sets the maximum number of times a message will be redelivered before it is considered a poisoned pill and returned to the broker so it can go to a Dead Letter Queue.
Sets the maximum delivery delay that will be applied if the
The delivery delay if
Should the redelivery policy use collision avoidance.
Should exponential back-off be used, i.e., to exponentially increase the timeout.
RedeliveryPolicy per Destination
As of ActiveMQ v5.7.0 you can now configure a RedeliveryPolicy on a per-destination bases. The
ActiveMQConnection factory class now exposes a RedeliveryPolicyMap property that allows to assign a RedeliveryPolicy using named destinations or using destination wildcards. The code snipped below shows how to configure a different RedeliveryPolicy for Topics and Queues.