jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: concurrency problem
Date Mon, 22 Aug 2005 12:49:29 GMT
hi walter,

On 8/22/05, Walter Raboch <wraboch@ingen.at> wrote:
> Hi Stefan,
> 
> >>the first InvalidItemStateException is correct.
> >>i'll investigate the ItemNotFoundException. i guess there's
> >>a 'synchronized' missing somewhere...
> >
> > this issue should be fixed now (r233511).
> 
> JackRabbit is still hanging on the Node.unlock() function.

that's a new issue. please post a jira bug with detailed instructions
how to reporduce the problem.

thanks
stefan

> 
> ... everything fine until here...
> s13: 4
> s13: 5
> s13: 6
> s13: 7   -> unlock()
> s14: started.
> s14: 1   -> session.getRootNode()
> s15: started.
> s15: 1
> s16: started.
> 
> I just find this failure during the first run (emtpy repository home
> directory). 2nd and 3th run are fine after killing the vm from first
> run, but with already initialized repository directory these time.
> 
> 1. rm -rf repository.home
> 2. run -> hang
> 3. kill
> 4. run -> ok
> 5. run -> ok
> 
> cheers,
> Walter
> 
>

Mime
View raw message