Thanks! Yeah, I thought about that. Okay I will set expiration time. Well, redelivery policy is working not as good as I supposed it to work. First of all, it blocks consumer to receive other messages until redelivery policy time reached. If you apply patch that makes consumer non-blocking then you might end up with a lot of threads being run. If, as it is in my case, you might have lots of messages unprocessed at the same time, then it is a bad solution. So I ended up with manual resending messages to the same queue with setting appropriate delivery delay if there still tries left. I had to manually calculate these delays, based on the same settings as ActiveMQ.NMS does. It allows me to unblock the consumer instantly and at the same time broker is responsible for redelivering messages.
-- View this message in context: http://activemq.2283324.n4.nabble.com/How-to-automatically-remove-messages-from-DLQ-tp4313129p4313775.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
