hi,

I dont have a test case for this.

However we can reproduce the deadlock in a multi-threaded cluster
environment. Many threads to read data, one thread to create and move
data, and one thread for deleting the data. Our application uses MySQL
persistence. When our application stops responding, we find all the
threads waiting on the ReaderLock.

I know this information is not very useful, but we have seen the hosts
hang multiple times.

Just FYI, we were using JR 1.5.5 earlier and had observed similar
deadlock (https://issues.apache.org/jira/browse/JCR-2237).

thanks for your help

regards
aasoj


On Tue, Aug 25, 2009 at 3:45 PM, KÖLL Claus<[email protected]> wrote:
> do you have a tescase ?
>
> greets
> claus
>
> -----Ursprüngliche Nachricht-----
> Von: aasoj j [mailto:[email protected]]
> Gesendet: Dienstag, 25. August 2009 06:15
> An: [email protected]
> Betreff: Deadlock in 1.6
>
> Hi,
>
> We are observing a deadlock in cluster deployment in the latest
> release 1.6. Here is the stack traces from one of the waiting threads
> ...
>
>   java.lang.Thread.State: WAITING (on object monitor)
>        at java.lang.Object.wait(Native Method)
>        at java.lang.Object.wait(Object.java:485)
>        at 
> EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock.acquire(Unknown
> Source)
>        - locked <0x0000002ad6cb9b40> (a
> EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock)
>        at 
> org.apache.jackrabbit.core.state.DefaultISMLocking$ReadLockImpl.<init>(DefaultISMLocking.java:84)
>        at 
> org.apache.jackrabbit.core.state.DefaultISMLocking$ReadLockImpl.<init>(DefaultISMLocking.java:78)
>        at 
> org.apache.jackrabbit.core.state.DefaultISMLocking.acquireReadLock(DefaultISMLocking.java:44)
>        at 
> org.apache.jackrabbit.core.state.SharedItemStateManager.acquireReadLock(SharedItemStateManager.java:1432)
>        at 
> org.apache.jackrabbit.core.state.SharedItemStateManager.getItemState(SharedItemStateManager.java:253)
>        at 
> org.apache.jackrabbit.core.state.LocalItemStateManager.getNodeState(LocalItemStateManager.java:107)
>        at 
> org.apache.jackrabbit.core.state.LocalItemStateManager.getItemState(LocalItemStateManager.java:172)
>        - locked <0x0000002b0e3be100> (a
> org.apache.jackrabbit.core.state.XAItemStateManager)
>        at 
> org.apache.jackrabbit.core.state.XAItemStateManager.getItemState(XAItemStateManager.java:260)
>        at 
> org.apache.jackrabbit.core.version.XAVersionManager.<init>(XAVersionManager.java:115)
>        at 
> org.apache.jackrabbit.core.XASessionImpl.createVersionManager(XASessionImpl.java:175)
>        at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:303)
>        at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:271)
>        at 
> org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java:105)
>        at 
> org.apache.jackrabbit.core.RepositoryImpl.createSessionInstance(RepositoryImpl.java:1517)
>        at 
> org.apache.jackrabbit.core.RepositoryImpl.createSession(RepositoryImpl.java:964)
>        at 
> org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1395)
> ---------------
>
> Thanks for your help
>
>
> regards
> aasoj
>

Reply via email to