I think this is the normal behaviour for 5.2. For 5.3, the message broker automatically sweeps destinations of expired messages every 30 seconds. You can change this default value via the 'expireMessagesPeriod' policyEntry attribute.
Joe ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide magellings wrote: > > Hello, > > I'm using ActiveMQ 5.2 and NMS 1.1. > > I'm sending non-persistent messages to a broker with an expiration time of > 1 hour. After one hour the messages are not deleted from the queue (can > see through jconsole and web console "number of pending messages"). After > one hour, no more messages are allowed to be sent to the queue because the > queue memory is exhausted. After one hour, consuming from the queue or > drilling down on the queue link in the web console triggers the deletion > of the messages. > > Is this normal behavior? I expected the broker to delete the messages as > they expire so that messages could keep being sent to the queue. Were > there any issues related to this resolved with ActiveMQ 5.3? > > I appreciate any help. > > -Thanks > -- View this message in context: http://old.nabble.com/ActiveMQ%2C-non-persistent-messages%2C-and-message-expiration-behaving-correctly----tp28477641p28480927.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
