Since version 5.4.0 there is an expiry task that by default will expire messages every 30 sec. Take a look at this thread http://activemq.2283324.n4.nabble.com/periodic-message-expiry-task-td2385521.html and related Jiras.
Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Wed, Jun 8, 2011 at 10:38 PM, agujral <[email protected]> wrote: > Does this means that if we have lot of messages with expiry and somehow > consumer is not able to process them then they will remain and will not be > removed,the expired messages will continue to use disk space . > > How do people handle this in practice since it can be possible that > producer > is generating lot of messages which consumer is not able to process , by > design we want to expired the old messages and remove them from the > queue.Should we have a consumer which remove those messages. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Expiry-of-messages-in-activemq-tp3581641p3583558.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
