we are using acivemq 5.13 with master slave setup with jdbc. we have enabled scheduling but the redelivery is working fine but looks like msgs are going to the DLQ after the maxredeliveries.
below is the sample activemq.xml file <broker advisorySupport="true" brokerName="broker" xmlns="http://activemq.apache.org/schema/core" persistent="true" schedulerDirectory="${activemq.data}/scheduler" schedulerSupport="true" useJmx="true"> <destinationPolicy> <policyMap> <policyEntries> <policyEntry queue=">"> <deadLetterStrategy> <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" /> </deadLetterStrategy> <pendingMessageLimitStrategy> <constantPendingMessageLimitStrategy limit="1000" /> </pendingMessageLimitStrategy> </policyEntry> <policyEntry topic=">"> <deadLetterStrategy> <individualDeadLetterStrategy topicPrefix="DLQ." useQueueForTopicMessages="true" /> </deadLetterStrategy> <pendingMessageLimitStrategy> <constantPendingMessageLimitStrategy limit="1000" /> </pendingMessageLimitStrategy> </policyEntry> </policyEntries> </policyMap> </destinationPolicy> <redeliveryPlugin fallbackToDeadLetter="true" sendToDlqIfMaxRetriesExceeded="true"> <redeliveryPolicyMap> <redeliveryPolicyMap> <redeliveryPolicyEntries> <redeliveryPolicy queue=">" maximumRedeliveries="1" redeliveryDelay="10000"/> </redeliveryPolicyEntries> <defaultEntry> <redeliveryPolicy maximumRedeliveries="1" initialRedeliveryDelay="5000" redeliveryDelay="1000"/> </defaultEntry> </redeliveryPolicyMap> </redeliveryPolicyMap> </redeliveryPlugin> -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-redelivery-is-not-working-with-5-13-tp4728713.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.