jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@day.com>
Subject Re: Concurrent Write issues with Jackrabbit
Date Wed, 28 Jul 2010 14:12:23 GMT

jackrabbit currently indeed serializes writes on the persistence
level. as a workaround you could batch multiple writes into a single
session save. though, I'm not sure if that's an option in your case.


On Wed, Jul 28, 2010 at 11:25, smjain <jain.sm@gmail.com> wrote:
> Hi All,
> We see a serious Write lock contention issue when we are trying to write to
> jackrabbit through different jcr sessions.
> We see huge number of threads waiting on a write lock when a session.save is
> done.
> All threads are writing to a different part of the repository but it seems
> as per the SharedItemStateManager
> design we have just one Write Lock  for the entire workspace.
> We tried with FineGrained Locks but that doesnt help either as it just
> optimizes read and still we have a single Write lock.
> Thoughts/Suggestions
> Regards
> Shashank
> --
> View this message in context: http://jackrabbit.510166.n4.nabble.com/Concurrent-Write-issues-with-Jackrabbit-tp2304674p2304674.html
> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.

View raw message