Re: [Exist-open] Locking Issue with Reading Binary Resources

[Wolfgang M. <wol...@gm...>]

> Well, digging into the code I see that both the getBinaryResource and
> readBinaryResource methods on NativeBroker use a write lock for reads.  That
> doesn't seem right.  If I change them to read locks, all my problems go away
> and everything loads much, much faster.
>
> Why would we need/want a write lock for a read of a binary resource?

Using a write lock in readBinaryResource is certainly not necessary.
However, it should not make a huge difference, since - for the
ReentrantReadWriteLock used here - both read and write are exclusive.
I cannot really explain why using a read lock makes your deadlock less
likely. It could be due to the deadlock detection taking some action.

Wolfgang