jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Short <...@benshort.co.uk>
Subject Re: session.save() taking too much of time when called by more than one thread.
Date Thu, 17 Dec 2009 13:05:32 GMT
Are you using the same session across multiple threads?

2009/12/17 sunild <sunil.dhage@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
>
>

Mime
View raw message