activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: Is this a kaha consistency problem?
Date Mon, 29 Dec 2008 17:24:27 GMT

On Dec 29, 2008, at 1:15 AM, Rob Davies wrote:

> which version are you using David ?

activemq trunk.  I have a couple local modifications but I don't think  
they cause this -- they are far from the kaha code.

thanks
david jencks


>
> On 25 Dec 2008, at 20:12, David Jencks wrote:
>
>> I'm working on trying to get the tck to pass with activemq trunk in  
>> geronimo.  When I run a failing test twice the server log shows  
>> stuff like this:
>>
>> 2008-12-25 11:37:08,567 ERROR [RecoveryListenerAdapter] Message id  
>> ID:pb.local-56923-1230232035140-2:13:1:1:1 could not be recovered  
>> from the data store - already dispatched
>> 2008-12-25 11:37:08,574 ERROR [RecoveryListenerAdapter] Message id  
>> ID:pb.local-56923-1230232035140-2:12:1:1:1 could not be recovered  
>> from the data store - already dispatched
>>
>> (lots and lots of times, each )
>>
>> This seems to be from RecoveryListenerAdapter:
>>
>>   public boolean recoverMessageReference(MessageId ref) throws  
>> Exception {
>>       Message message = this.store.getMessage(ref);
>>       if (message != null) {
>>           return recoverMessage(message);
>>       } else {
>>           LOG.error("Message id " + ref + " could not be recovered  
>> from the data store - already dispatched");
>>       }
>>       return false;
>>   }
>>
>>
>> My guess is that the reference store has a reference to a message  
>> that is no longer in the message store.  Is this a problem or an  
>> expected state?  If its unexpected, does anyone have any ideas on  
>> where to look to figure out how we got into this state?
>>
>> thanks
>> david jencks
>>
>


Mime
View raw message