activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kentdorsey <kentdor...@gmail.com>
Subject Re: Persistent messages not being cleaned up for non-durable Topic
Date Sat, 09 Sep 2006 02:08:00 GMT



kentdorsey wrote:
> 
> 
> The questions:
> 
> What is triggering the above select statement?
> 
> 

Looking at the JournalPersistenceAdapter source, every five minutes, a
ClockTicket invokes JournalPersistenceAdapter.checkpoint(false), which in
our case then  invokes JDBCPersistenceAdapter.cleanup(), which eventually
invokes the above select statement via
DefaultJDBCAdapter.doGetExpiredMessages().

Also, looking at the JDBCPersistenceAdapatersource, every five minutes, a
ClockTicket invokes JDBCPersistenceAdapater.cleanup(), which also invokes
the above select statement via DefaultJDBCAdapter.doGetExpiredMessages().

There is a flag, isAutoCleanupExpiredMessages(), which affects the
execution.

New questions:

Do both adapters run the cleanup process every five minutes using
configuration defaults?
-- 
View this message in context: http://www.nabble.com/Persistent-messages-not-being-cleaned-up-for-non-durable-Topic-tf2242336.html#a6219674
Sent from the ActiveMQ - User forum at Nabble.com.


Mime
View raw message