Our ActiveMQ 5.1.0 server takes an inordinately long time to recover from a
crash. I mean a couple of hours is not unusual in our case. We do use
"topics". I am providing the log messages from ActiveMQ and would appreciate
if someone can tell us what our options are to reduce the crash recovery
times.

There are a few "topics" in the log messages below that do not have a
receiver anymore. We have not been able to find a way to delete them (would
appreciate some help to find out what commands we can use to delete them).
However, I do not believe that long recovery times are associated with just
those topics. I have also seen this problem on another instance of ActiveMQ
where we do not have any orphan topics.

Here are the log messages:

2009-03-16 14:29:26,903 [main           ] INFO  BrokerService                 
- Using Persistence Adapter:
AMQPersistenceAdapter(/usr/dev/apache-activemq-5.1.0/data)
2009-03-16 14:29:26,905 [main           ] INFO  BrokerService                 
- ActiveMQ 5.1.0 JMS Message Broker (localhost) is starting
2009-03-16 14:29:26,905 [main           ] INFO  BrokerService                 
- For help or more information please see: http://activemq.apache.org/
2009-03-16 14:29:26,911 [main           ] INFO  AMQPersistenceAdapter         
- AMQStore starting using directory: /usr/dev/apache-activemq-5.1.0/data
2009-03-16 14:29:26,949 [main           ] INFO  KahaStore                     
- Kaha Store using data directory
/usr/dev/apache-activemq-5.1.0/data/kr-store/state
2009-03-16 14:29:27,088 [main           ] INFO  AMQPersistenceAdapter         
- Active data files: []
2009-03-16 14:29:27,092 [main           ] WARN  AMQPersistenceAdapter         
- The ReferenceStore is not valid - recovering ...
2009-03-16 14:29:29,021 [main           ] INFO  KahaStore                     
- Kaha Store successfully deleted data directory
/usr/dev/apache-activemq-5.1.0/data/kr-store/data
2009-03-16 14:29:29,034 [main           ] INFO  KahaReferenceStoreAdapter     
- Recovering subscriber state for durable subscriber: SubscriptionInfo
{subscribedDestination = topic://INDEX.ITEM.T, destination =
topic://INDEX.ITEM.T, clientId = index-indexer-01, subscriptionName =
INDEX.ITEM.T.DURABLE.SUBSCRIPTION, selector = null}
2009-03-16 14:29:29,034 [main           ] INFO  KahaStore                     
- Kaha Store using data directory
/usr/dev/apache-activemq-5.1.0/data/kr-store/data
2009-03-16 14:29:29,056 [main           ] INFO  KahaReferenceStoreAdapter     
- Recovering subscriber state for durable subscriber: SubscriptionInfo
{subscribedDestination = topic://INDEX.ITEM, destination =
topic://INDEX.ITEM, clientId = merlot1-index-index-01, subscriptionName =
INDEX.ITEM.DURABLE.SUBSCRIPTION, selector = null}
2009-03-16 14:29:29,058 [main           ] INFO  KahaReferenceStoreAdapter     
- Recovering subscriber state for durable subscriber: SubscriptionInfo
{subscribedDestination = topic://INDEX.ITEM.T, destination =
topic://INDEX.ITEM.T, clientId = index-indexer-ec2-01, subscriptionName =
INDEX.ITEM.T.DURABLE.SUBSCRIPTION, selector = null}
2009-03-16 14:29:29,060 [main           ] INFO  KahaReferenceStoreAdapter     
- Recovering subscriber state for durable subscriber: SubscriptionInfo
{subscribedDestination = topic://INDEX.ITEM, destination =
topic://INDEX.ITEM, clientId = merlot1-index-indexer-01, subscriptionName =
INDEX.ITEM.DURABLE.SUBSCRIPTION, selector = null}
@                                                                               
                                    
-- 
View this message in context: 
http://www.nabble.com/Long-recovery-time-for-ActiveMQ-tp22545943p22545943.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to