Hi There appears to be an issue with expired messages on ActiveMQ version 5.2.0. Expired messages are not immediately moved to the DLQ when they expire. Instead they remain in the queue until they have exceeded their expiry date by several minutes AND another message is delivered to the queue. When these two conditions are met the expired messages are moved to the DLQ. However, I have been unable to predict with any accuracy exactly when messages will be moved.
It seems that this issue is covered by https://issues.apache.org/activemq/browse/AMQ-1112, which indicates that the issue is resolved in version 5.3.0. Is it possible to obtain a build of version of 5.3.0? When is it due for release? I have attempted to use version 4.1 (with the patched web-console) but this version does not appear to expire messages into the DLQ at all. Of course, if you have any suggestions as to how I can overcome this limitation then I would be very grateful. Unfortunately, this functionality is key to the system I am using and if I can't overcome it (without resorting to writing a standalone housekeeping application) I will have to use another broker. This is disappointing as I have been otherwise very impressed with ActiveMQ. Thanks -- View this message in context: http://www.nabble.com/Messages-not-being-expired-onto-DLQ-tp22851111p22851111.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
