Hi,

I want to use the „retryMessage(messageId)“ QueueViewMBean functionality to
move the failed messages from DLQ back to the original destination. Using
activemq v5.11.1 with following policyEntry configuration:

                    <amq:policyEntry queue="abc.inbound"
                                     producerFlowControl="true"
                                     timeBeforeDispatchStarts="2000"
                                     reduceMemoryFootprint="true"
                                     queuePrefetch="5">
                        <amq:deadLetterStrategy>
                            
                            <amq:individualDeadLetterStrategy
                            queuePrefix="DLQ."
useQueueForQueueMessages="true" />
                        </amq:deadLetterStrategy>
                        <amq:pendingQueuePolicy>
                            <amq:fileQueueCursor />
                        </amq:pendingQueuePolicy>
                    </amq:policyEntry>

Running from JConsole operation returns „true“, the message dissapears from
the „DLQ.abc.inbound“ but never gets to the original „abc.inbound“
destination. Only after restart of the Tomcat the message is being properly
consumed by the „abc.inbound“ consumer. The same happens when using the
„moveMessageTo(messageId, destinationName)“ operation.

And also when using „individualDeadLetterStrategy“, created DLQ
(„queuePrefix.originalDestinationName“) has JMX property „DLQ=false“
therefore the operation „retryMessages()“ can not be runned on such DLQ’s.
Is there any workaround?

Please advise,
many thanks,
Boris




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Moving-messages-with-QueueViewMBean-moveMessage-or-QueueViewMBean-retryMessage-does-not-work-tp4702700.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to