i think in your case, it might be best to use gcInactiveDestination w/ TTL on the message as gary suggests.
You should be able to build up your own monitoring solution using Advisory messages, and tracking how long dests have been idle. Again, camel would be suitable for this. It might also make sense to expose the "isActive" method via JMX as well as allow gc the destination if it's inactive and has messages. You can open a JIRA for that. On Mon, Sep 23, 2013 at 12:59 PM, wcpolicarpio < walter.policar...@morgansolar.com> wrote: > Thank you Christian and Gary for responding to my question. Sorry, I forgot > to mention that the destination should be idle for a period of time, let > say > a day. Is there a way to know how long the destination is idle before > deleting? > > gcInactiveDestination only works when there are no pending messages and > connected consumers. > > Regards > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Remove-message-queue-after-a-day-with-or-with-or-without-a-message-tp4671669p4671749.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
