Replace regular DLQ handling with redelivery via a resend to the original destinationafter a delayA destination matching RedeliveryPolicy controls the quantity and delay for re-sendsIf there is no matching policy or an existing policy limit is exceeded by defaultregular DLQ processing resumes. This is controlled via sendToDlqIfMaxRetriesExceededand fallbackToDeadLetter
What to do if there is no matching redelivery policy for a destination.when true, the region broker DLQ processing will be used via sendToDeadLetterQueuewhen false, there is no action
What to do if the maxretries on a matching redelivery policy is exceeded.when true, the region broker DLQ processing will be used via sendToDeadLetterQueuewhen false, there is no action
Wildcard: ANY attribute from ANY namespace OTHER than 'http://activemq.apache.org/schema/core'
What to do if there is no matching redelivery policy for a destination.when true, the region broker DLQ processing will be used via sendToDeadLetterQueuewhen false, there is no action
What to do if the maxretries on a matching redelivery policy is exceeded.when true, the region broker DLQ processing will be used via sendToDeadLetterQueuewhen false, there is no action