jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@gmx.net>
Subject Re: Intermittent JackRabbit dead lock with concurrent QueryImpl.execute() and NodeImpl.getProperty()
Date Fri, 09 May 2008 12:56:16 GMT
Hi,

sbarriba wrote:
> I just noticed
> http://www.nabble.com/-jira--Created:-(JCR-1334)-Deadlock-with-XA-enabled-td
> 14997630.html. Could that be related given we've deployed JackRabbit as a
> RAR module within Weblogic?

I don't think those are related, both threads only read from the repository.

> Blocked lock chains
> ===================
>     Chain 30:
>     "[ACTIVE] ExecuteThread: '55' for queue: 'weblogic.kernel.Default
>     (self-tuning)'" id=27350 idx=0x1cc tid=26815 waiting for
>     EDU/oswego/cs/dl/util/concurrent/WriterPreferenceReadWriteLock$ReaderLoc
>     k@0xbd7c718 held by:
>     "[ACTIVE] ExecuteThread: '50' for queue: 'weblogic.kernel.Default
> (self-tuning)'" id=27345 idx=0x220 tid=26810 in chain 1
> 
> Chain 36:
> "[ACTIVE] ExecuteThread: '50' for queue: 'weblogic.kernel.Default
> (self-tuning)'" id=27345 idx=0x220 tid=26810 waiting for
> EDU/oswego/cs/dl/util/concurrent/WriterPreferenceReadWriteLock$ReaderLoc
> k@0xbd7c718 held by:
> "[ACTIVE] ExecuteThread: '55' for queue: 'weblogic.kernel.Default
> (self-tuning)'" id=27350 idx=0x1cc tid=26815 in chain 1

this is pretty strange because both threads try to acquire a read lock, which is 
guaranteed to not block, unless some other thread owns the write lock.

even more strange, the JVM claims that *both* threads hold the same monitor!

-> ReaderLock@0xbd7c718 held by: "[ACTIVE] ExecuteThread: '55' [...]
-> ReaderLock@0xbd7c718 held by: "[ACTIVE] ExecuteThread: '50' [...]

maybe a JVM upgrade will help?

regards
  marcel

Mime
View raw message