jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <george.sib...@bt.com>
Subject RE: Jackrabbit 1.6.0 Write Performance
Date Mon, 12 Apr 2010 15:13:21 GMT
Yes, exactly.

Many thanks. 

-----Original Message-----
From: Justin Edelson [mailto:justinedelson@gmail.com] 
Sent: 12 April 2010 15:38
To: dev@jackrabbit.apache.org
Subject: Re: Jackrabbit 1.6.0 Write Performance

This looks like https://issues.apache.org/jira/browse/JCR-2579 ?

On 4/12/10 9:25 AM, george.sibley@bt.com wrote:
> Thomas
> 
> We still hit problems when we attempted to add nodes, concurrently, to existing nodes
(I think the message was something like "attempting to update a node that is already being
updated"). We had to lock the node, update, and then release.  
> 
> Regards
> 
> George
> 
> -----Original Message-----
> From: Thomas Müller [mailto:thomas.mueller@day.com]
> Sent: 12 April 2010 12:57
> To: dev@jackrabbit.apache.org
> Subject: Re: Jackrabbit 1.6.0 Write Performance
> 
> Hi,
> 
>> With regard to concurrency, are there any plans for jackrabbit to support concurrency
out of the box?
> 
> If you use one session for each thread then it should already work.
> It's a bug if it doesn't.
> 
> In any case I would use one session per thread, no matter if a future version of Jackrabbit
supports it or not.
> 
> Regards,
> Thomas


Mime
View raw message