Hello,
Well, I can't speak to the actual problem, but it seems that you have
quite a number
of durable subscribers that are being recovered.
In your eMail you mention that topics are recovered that don't have
any receivers anymore.
Well , that's kind of the point for a durable subscription. If the
subscriber has gone offline and
is not needed any longer you should make sure to unsubscribe from the
topic.
It might also be an option to consider message time outs. AFAIK timed
out messages would
be cleaned out upon broker start, but I need to verify that. Perhaps
someone could confirm / deny
this assumption.
Hope that helps
Andreas
On Mar 16, 2009, at 9:25 PM, naveenshankar wrote:
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.
---
Mit freundlichen Grüssen - Kind Regards
Andreas Gies
Principal Consultant
Open Source Center of Competence
Progress Software GmbH
Agrippinawerft 26
50678 Köln
E-Mail ag...@progress.com
Direct Line +49 (0)9953 980349
Mobile +49 (0)170 5759611
Skype +44 (0)20 3239 2922
Skype +353 (0)1 443 4971
Skype +1 (0)781 262 0168
http://www.progress.com
http://fusesource.com
http://open-source-adventures.blogspot.com
-------------------------------------------------------
Progress Software GmbH
Sitz der Gesellschaft: Agrippinawerft 26, 50678 Koeln;
Niederlassung: Fuerstenrieder Str. 279, 81377 Muenchen
Amtsgericht Koeln, HRB 15620;
Geschaeftsfuehrung: David Ireland
-------------------------------------------------------
