It's pretty difficult for people to offer hints or suggestions about what's not working when you haven't told us what's actually happening, nor what version of ActiveMQ you're using. Hopefully you can provide more details about what you observed, to help people help you.
For your TTL settings, what behavior are you expecting, and what are you actually seeing? For those settings, I'd expect the following: * If the message is sent without a TTL value, a TTL value of 30 seconds would be applied by the broker upon receipt. * If the message is sent with a TTL value <= 30 seconds, the TTL value would be left unchanged by the broker. * If the message is sent with a TTL value > 30 seconds, a TTL value of 30 seconds would be applied by the broker upon receipt How does that compare to what you're actually seeing when you examine the message headers? Note that the TimeStampingBrokerPlugin doesn't expire messages, only change the TTL header so that the *broker* can expire the messages if needed, so to know if the plugin is working, you need to look at the message headers. Also note that if you have no consumers on the queue, ActiveMQ does not delete expired messages, so you'd only see deletions of expired messages if you subsequently connected a consumer to the queue. So if you were declaring the TimeStampingBrokerPlugin not to work based on the broker not deleting expired messages on a queue with no consumers, then that's not a valid test of whether message expiration works. For your statement that messages are not DLQ'ed after exceeding the maximum redelivery count, what redelivery policy have you set, and how many redeliveries are you seeing? Also, what ack mode are you using? https://stackoverflow.com/questions/52197961/activemq-broker-redelivery-and-dlq-not-woking points out one situation in which you wouldn't see redelivery (broker-side, in that case), but since you're talking about exceeding the maximum redelivery count, that appears to mean that you're getting infinite redelivery whereas that post describes a situation where the poster doesn't get any redelivery at all, so they sound like different problems. Tim On Tue, Mar 26, 2019 at 7:19 AM W.Y <wyan...@gmail.com> wrote: > > With below setting (at activemq.xml ) > > Set Time to Live does not work, > > Set DeadLetterQueue for exceeding maximum redelivery also does not work > > The settings are from below documents > > http://activemq.apache.org/message-redelivery-and-dlq-handling.html > > http://activemq.apache.org/timestampplugin.html > > as hints or suggestiones are more than weclome! > > > <http://activemq.2283324.n4.nabble.com/file/t379460/Unbenannt.png> > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
