Hi, I am using ActiveMQ 5.0 on Windows XP and Windows 2003.
My program send a persistent message to queue with timeToLive = 3 seconds. The message enter into ActiveMQ.DLQ after timeout. Then I have start a consumer to the queue with connection URI below, where "jms.redeliveryPolicy.maximumRedeliveries=-1" means unlimited redelivery according to documnetation: tcp://127.0.0.1:61616?wireFormat.maxInactivityDuration=0&jms.redeliveryPolicy.maximumRedeliveries=-1 Then I stop the consumer, and send another persistent message with timeToLive = 3 seconds. This time the message do not enter ActiveMQ.DLQ after timeout. After a while, I start my consumer again and expect the consumer able to receive the message. But once the consumer connected to ActiveMQ, then pending message was enter into ActiveMQ.DLQ. So below is my questions: 1) It is my assumption invalid and this is this the expected behavior of ActiveMQ? or this is some sort of bugs in ActiveMQ? 2) Anyway to tweak the producer/consumer/queue so that consumer can receive the message even it already exceed the timeout and redelivery? Thank you. Truly, Thiam Teck -- View this message in context: http://www.nabble.com/Message-enter-ActiveMQ.DLQ-after-consumer-reconnect-tp16306220s2354p16306220.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
