river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: Bug fixing
Date Mon, 25 Oct 2010 16:15:16 GMT
I've made some progress on one form of failure, a resource remaining 
available after its lease was scheduled to expire.

If the test pauses, e.g due to an inserted Thread.sleep, between 
creating the lease and probing it for the first time, the test passes. 
The effect of either of these actions is to delay the probe until after 
the lease has expired. Incidentally, hooking up to the Eclipse debugger 
was very helpful in discovering this behavior. The first indication was 
when I spent a few minutes investigating at a breakpoint, let it 
continue, and the test passed.

If the test gets to the probe point before the lease is due to expire, 
it goes into a polling loop. No matter how long it stays in the polling 
loop, the lease does not expire. Somehow, the probe loop has the effect 
of preventing expiration.

I would like to understand the rules for lease expiration. What actions 
should extend a lease? Is the lease manager required to expire it on 
schedule? (Even if it is not required to expire the lease I still need 
to find out whether the non-expiration is deliberate design or due to a 

Can anyone point me to documentation or a tutorial that would help?



Patricia Shanahan wrote:
> I've done a preliminary javaspace test:
>      [java] # of tests started   = 259
>      [java] # of tests completed = 259
>      [java] # of tests skipped   = 3
>      [java] # of tests passed    = 243
>      [java] # of tests failed    = 16
> The failures seem to fall into a few clusters. I'll start on one of them 
> tomorrow.
> Patricia
> On 10/20/2010 1:44 PM, Jonathan Costers wrote:
>> My vote would go to the "javaspace" test category.
>> Last time I ran that one (250 or so tests IIRC) I got 16 failures.
>>> On 10/19/2010 4:08 PM, Patricia Shanahan wrote:
>>> Any votes on my next bug hunt? For example, are there bug reports in 
>>> Jira
>>> that really need to be fixed before the next release?

View raw message