You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@jackrabbit.apache.org by Ben Short <be...@benshort.co.uk> on 2009/12/17 14:05:32 UTC

Re: session.save() taking too much of time when called by more than one thread.

Are you using the same session across multiple threads?

2009/12/17 sunild <su...@coreobjects.com>:
> Hi,
>
> In my application, there are multiple threads going to access repository
> simultaneosly.
>
> I have tried using node.lock() and unlock() but faced few problems.
> --session have pending changes, item got locked-cannot lock the node, etc
>
> Finally I decided to go with ReentrantReadWriteLock.
>
> But I see that whenever more than one thread are trying to save the session,
> it is taking much more time.
>
> Can you help me out.  Please suggest me the suitable solutions.
>
> Regards,
> Sunil Dhage
>
>

Re: session.save() taking too much of time when called by more than one thread.

Posted by sunild <su...@coreobjects.com>.

No,
I am using different session for each thread.

Regards,
Sunil Dhage

Ben Short wrote:
> Are you using the same session across multiple threads?
>
> 2009/12/17 sunild <su...@coreobjects.com>:
>   
>> Hi,
>>
>> In my application, there are multiple threads going to access repository
>> simultaneosly.
>>
>> I have tried using node.lock() and unlock() but faced few problems.
>> --session have pending changes, item got locked-cannot lock the node, etc
>>
>> Finally I decided to go with ReentrantReadWriteLock.
>>
>> But I see that whenever more than one thread are trying to save the session,
>> it is taking much more time.
>>
>> Can you help me out.  Please suggest me the suitable solutions.
>>
>> Regards,
>> Sunil Dhage
>>
>>
>>