HI,

Do non persistent messages with a TTL ever get removed out of the brokers
message store? I wrote a test that sends a non persistent message with a TTL
of 1ms and then tries to consume this message. What I have noticed is that
every time I run this test the broker tries to redeliver the previously
expired message as well as the newly expired message but the
ActiveMQMessageConsumer rejects it and outputs multiple "Received expired
message:" debug log record. I waited for an hour to see if the thread that
deletes messages out of the persistent store cleaned up these messages as
well but it doesn't seem to.

I'm using jms for heartbeating clients and I want to use the TTL
functionality to remove stale heartbeat requests but if the they are going
to cause a memory leak in the broker i won't be able to do this.
-- 
View this message in context: 
http://www.nabble.com/Non-Persistent-queue-message-TTL-tf2492842.html#a6949731
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to