Thanks for your help Tim!
The system has been smooth since.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
You've probably already tried this and found it out, but persistent
messages are the normal case for the SharedDeadLetterStrategy, so they'll
be processed even if processExpired is false. Non-persistent messages are
not sent to the DLQ by default, which is why you've explicitly enabled that
via pro
Will this work on messages that are marked as 'Persistent'?
I have changed the config to now have processexpired to false. I understand
why the previous one would be circular in processing.
Just wondering about persistent messages.
Chris
--
Sent from: http://activemq.2283324.n4.nabble.com/Act
I believe the problem is that your current configuration has your messages
expire after 24 hours on the DLQ, only to be deleted and sent to. the
DLQ. I believe this is what is referred to by the warning in the Setting
Expiration on Messages in the DLQ section of
http://activemq.apache.org/messa
Hi everyone!
I am having an issue where a subscriber is not running and messages get sent
to the DLQ. The messages are marked 'Persistent'. Is there a way I can make
the DLQ 'persistent' messages to get deleted after a 24h period?
I don't care about redelivery or any kind of checking at this poin
