Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-Id: <4AED9D8E-A457-4672-A959-A70F1FEE9416@progress.com>
From: Andreas Gies <agies@progress.com>
To: users@activemq.apache.org
In-Reply-To: <22545943.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Long recovery time for ActiveMQ
Date: Fri, 20 Mar 2009 22:16:53 +0100
References: <22545943.post@talk.nabble.com>

Hello,

Well, I can't speak to the actual problem, but it seems that you have =20=

quite a number
of durable subscribers that are being recovered.

In your eMail you mention that topics are recovered that don't have =20
any receivers anymore.
Well , that's kind of the point for a durable subscription. If the =20
subscriber has gone offline and
is not needed any longer you should make sure to unsubscribe from the =20=

topic.

It might also be an option to consider message time outs. AFAIK timed =20=

out messages would
be cleaned out upon broker start, but I need to verify that. Perhaps =20
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 =20=

> 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 =20
> appreciate
> if someone can tell us what our options are to reduce the crash =20
> 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 =20=

> (would
> appreciate some help to find out what commands we can use to delete =20=

> them).
> However, I do not believe that long recovery times are associated =20
> with just
> those topics. I have also seen this problem on another instance of =20
> 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/=20=

> 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  =20
> KahaReferenceStoreAdapter
> - Recovering subscriber state for durable subscriber: SubscriptionInfo
> {subscribedDestination =3D topic://INDEX.ITEM.T, destination =3D
> topic://INDEX.ITEM.T, clientId =3D index-indexer-01, subscriptionName =
=3D
> INDEX.ITEM.T.DURABLE.SUBSCRIPTION, selector =3D 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  =20
> KahaReferenceStoreAdapter
> - Recovering subscriber state for durable subscriber: SubscriptionInfo
> {subscribedDestination =3D topic://INDEX.ITEM, destination =3D
> topic://INDEX.ITEM, clientId =3D merlot1-index-index-01, =20
> subscriptionName =3D
> INDEX.ITEM.DURABLE.SUBSCRIPTION, selector =3D null}
> 2009-03-16 14:29:29,058 [main           ] INFO  =20
> KahaReferenceStoreAdapter
> - Recovering subscriber state for durable subscriber: SubscriptionInfo
> {subscribedDestination =3D topic://INDEX.ITEM.T, destination =3D
> topic://INDEX.ITEM.T, clientId =3D index-indexer-ec2-01, =20
> subscriptionName =3D
> INDEX.ITEM.T.DURABLE.SUBSCRIPTION, selector =3D null}
> 2009-03-16 14:29:29,060 [main           ] INFO  =20
> KahaReferenceStoreAdapter
> - Recovering subscriber state for durable subscriber: SubscriptionInfo
> {subscribedDestination =3D topic://INDEX.ITEM, destination =3D
> topic://INDEX.ITEM, clientId =3D merlot1-index-indexer-01, =20
> subscriptionName =3D
> INDEX.ITEM.DURABLE.SUBSCRIPTION, selector =3D null}
> @
> --=20
> 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=FCssen - Kind Regards
Andreas Gies
Principal Consultant
Open Source Center of Competence

Progress Software GmbH
Agrippinawerft 26
50678 K=F6ln

E-Mail      	agies@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
-------------------------------------------------------