You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by emilyj <ja...@yahoo.com> on 2010/08/06 16:06:21 UTC
Kaha Store is not valid
Hi,
I am currently running ActiveMQ 5.2.0 on HP Blades. I have a master-slave
configuration set up with Veritas CFS.
I've noticed whenever I prompt a failover, the slave that becomes master is
unable to recover cleanly.
The following is in the log:
2010-08-05 21:33:59,841 WARN AMQPersistenceAdapter - Waiting to
Lock the Store /TM/activemq-data
2010-08-05 21:37:34,286 INFO AMQPersistenceAdapter - AMQStore
starting using directory: /TM/activemq-data
2010-08-05 21:37:34,413 INFO KahaStore - Kaha Store
using data directory /TM/activemq-data/kr-store/state
2010-08-05 21:37:34,529 INFO AMQPersistenceAdapter - Active data
files: []
2010-08-05 21:37:34,531 WARN AMQPersistenceAdapter - The
ReferenceStore is not valid - recovering ...
2010-08-05 21:37:35,190 INFO KahaStore - Kaha Store
successfully deleted data directory /TM/activemq-data/kr-store/data
2010-08-05 21:37:35,195 INFO KahaReferenceStoreAdapter - Recovering
subscriber state for durable subscriber: SubscriptionInfo {subscribedD
estination = topic://tcmquery.ReutersMessagesB, destination =
topic://tcmquery.ReutersMessagesB, clientId = hdcConsBSecondary,
subscriptionName
= hdcConsBSecondary, selector = null}
2010-08-05 21:37:35,196 INFO KahaStore - Kaha Store
using data directory /TM/activemq-data/kr-store/data
2010-08-05 21:37:35,247 INFO KahaReferenceStoreAdapter - Recovering
subscriber state for durable subscriber: SubscriptionInfo {subscribedD
estination = topic://tcmquery.ReutersMessagesC, destination =
topic://tcmquery.ReutersMessagesC, clientId = hdcConsCSecondary,
subscriptionName
= hdcConsCSecondary, selector = null}
And then it repeatedly tries to recover the same message and fills the log.
2010-08-05 22:02:33,188 ERROR RecoveryListenerAdapter - Message id
ID:htcp-tmsgws01h-65396-1280502391087-0:0:1:1:12119 could not be recovered
from the data store - already dispatched
If I remove the data directory it works fine, but then I lose messages.
I noticed other post similar to this and it seems the issue was fixed in
5.3, but at this point I can't upgrade. Is there a workaround for 5.2?
Thanks.
--
View this message in context: http://old.nabble.com/Kaha-Store-is-not-valid-tp29356453p29356453.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Kaha Store is not valid
Posted by emilyj <ja...@yahoo.com>.
Thanks Gary for the response. So release 5.2 is pretty much useless if
recovery is needed?
Gary Tully wrote:
>
> there is no 5.2 workaround.
>
> On 6 August 2010 15:06, emilyj <ja...@yahoo.com> wrote:
>>
>> Hi,
>>
>> I am currently running ActiveMQ 5.2.0 on HP Blades. I have a
>> master-slave
>> configuration set up with Veritas CFS.
>>
>> I've noticed whenever I prompt a failover, the slave that becomes master
>> is
>> unable to recover cleanly.
>>
>> The following is in the log:
>> 2010-08-05 21:33:59,841 WARN AMQPersistenceAdapter - Waiting to
>> Lock the Store /TM/activemq-data
>> 2010-08-05 21:37:34,286 INFO AMQPersistenceAdapter - AMQStore
>> starting using directory: /TM/activemq-data
>> 2010-08-05 21:37:34,413 INFO KahaStore - Kaha Store
>> using data directory /TM/activemq-data/kr-store/state
>> 2010-08-05 21:37:34,529 INFO AMQPersistenceAdapter - Active
>> data
>> files: []
>> 2010-08-05 21:37:34,531 WARN AMQPersistenceAdapter - The
>> ReferenceStore is not valid - recovering ...
>> 2010-08-05 21:37:35,190 INFO KahaStore - Kaha Store
>> successfully deleted data directory /TM/activemq-data/kr-store/data
>> 2010-08-05 21:37:35,195 INFO KahaReferenceStoreAdapter - Recovering
>> subscriber state for durable subscriber: SubscriptionInfo {subscribedD
>> estination = topic://tcmquery.ReutersMessagesB, destination =
>> topic://tcmquery.ReutersMessagesB, clientId = hdcConsBSecondary,
>> subscriptionName
>> = hdcConsBSecondary, selector = null}
>> 2010-08-05 21:37:35,196 INFO KahaStore - Kaha Store
>> using data directory /TM/activemq-data/kr-store/data
>> 2010-08-05 21:37:35,247 INFO KahaReferenceStoreAdapter - Recovering
>> subscriber state for durable subscriber: SubscriptionInfo {subscribedD
>> estination = topic://tcmquery.ReutersMessagesC, destination =
>> topic://tcmquery.ReutersMessagesC, clientId = hdcConsCSecondary,
>> subscriptionName
>> = hdcConsCSecondary, selector = null}
>>
>> And then it repeatedly tries to recover the same message and fills the
>> log.
>> 2010-08-05 22:02:33,188 ERROR RecoveryListenerAdapter - Message id
>> ID:htcp-tmsgws01h-65396-1280502391087-0:0:1:1:12119 could not be
>> recovered
>> from the data store - already dispatched
>>
>> If I remove the data directory it works fine, but then I lose messages.
>> I noticed other post similar to this and it seems the issue was fixed in
>> 5.3, but at this point I can't upgrade. Is there a workaround for 5.2?
>>
>> Thanks.
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Kaha-Store-is-not-valid-tp29356453p29356453.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
>
--
View this message in context: http://old.nabble.com/Kaha-Store-is-not-valid-tp29356453p29398808.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Kaha Store is not valid
Posted by Gary Tully <ga...@gmail.com>.
there is no 5.2 workaround.
On 6 August 2010 15:06, emilyj <ja...@yahoo.com> wrote:
>
> Hi,
>
> I am currently running ActiveMQ 5.2.0 on HP Blades. I have a master-slave
> configuration set up with Veritas CFS.
>
> I've noticed whenever I prompt a failover, the slave that becomes master is
> unable to recover cleanly.
>
> The following is in the log:
> 2010-08-05 21:33:59,841 WARN AMQPersistenceAdapter - Waiting to
> Lock the Store /TM/activemq-data
> 2010-08-05 21:37:34,286 INFO AMQPersistenceAdapter - AMQStore
> starting using directory: /TM/activemq-data
> 2010-08-05 21:37:34,413 INFO KahaStore - Kaha Store
> using data directory /TM/activemq-data/kr-store/state
> 2010-08-05 21:37:34,529 INFO AMQPersistenceAdapter - Active data
> files: []
> 2010-08-05 21:37:34,531 WARN AMQPersistenceAdapter - The
> ReferenceStore is not valid - recovering ...
> 2010-08-05 21:37:35,190 INFO KahaStore - Kaha Store
> successfully deleted data directory /TM/activemq-data/kr-store/data
> 2010-08-05 21:37:35,195 INFO KahaReferenceStoreAdapter - Recovering
> subscriber state for durable subscriber: SubscriptionInfo {subscribedD
> estination = topic://tcmquery.ReutersMessagesB, destination =
> topic://tcmquery.ReutersMessagesB, clientId = hdcConsBSecondary,
> subscriptionName
> = hdcConsBSecondary, selector = null}
> 2010-08-05 21:37:35,196 INFO KahaStore - Kaha Store
> using data directory /TM/activemq-data/kr-store/data
> 2010-08-05 21:37:35,247 INFO KahaReferenceStoreAdapter - Recovering
> subscriber state for durable subscriber: SubscriptionInfo {subscribedD
> estination = topic://tcmquery.ReutersMessagesC, destination =
> topic://tcmquery.ReutersMessagesC, clientId = hdcConsCSecondary,
> subscriptionName
> = hdcConsCSecondary, selector = null}
>
> And then it repeatedly tries to recover the same message and fills the log.
> 2010-08-05 22:02:33,188 ERROR RecoveryListenerAdapter - Message id
> ID:htcp-tmsgws01h-65396-1280502391087-0:0:1:1:12119 could not be recovered
> from the data store - already dispatched
>
> If I remove the data directory it works fine, but then I lose messages.
> I noticed other post similar to this and it seems the issue was fixed in
> 5.3, but at this point I can't upgrade. Is there a workaround for 5.2?
>
> Thanks.
>
> --
> View this message in context: http://old.nabble.com/Kaha-Store-is-not-valid-tp29356453p29356453.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com