Thanks Joe...this looks to be correct. Did a search on that attribute and found this.
https://issues.apache.org/activemq/browse/AMQ-1112 As an FYI to others, when switching to use persistent messaging (w/ JDBC master/slave) the memory is not exhausted and the messages are deleted periodically. The counters however do not update appropriately but for us this is not a big deal. We look forward to upgrading from v5.2 when v5.4 comes. We look forward to the CRON functionality. Joe Fernandez wrote: > > 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----tp28477641p28487400.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
