jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Köll (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-1334) Deadlock with XA enabled
Date Mon, 10 Mar 2008 10:17:46 GMT

    [ https://issues.apache.org/jira/browse/JCR-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576929#action_12576929

Claus Köll commented on JCR-1334:

hi marcel,
i do not have configured a extra ISMLocking in my repository.xml file because
i have applied the patched code directly on the DefaultISMLocking Class
My node have only the mix:referenceable and mix:lockable types.
If i look into the last stacktrace i have added i see that the deadlock comes from the SharedItemStateManager.getItemState
This calls VersionItemStateProvider.hasItemState. 
I do not know why this will be called on my node that has no mix:versionable as mixintype

Anyway .. it tries to acquire a ReadLock with the DefaultISMLocking hold by versionstorage.
On the rwLock Object of that instance there was never called downgrade so the rwLock has a
other Thread than
the rwLock Object of the DefaultISMLocking hold by the SharedItemStateManager.

If we call rwLock.setActiveWriter(Thread.currentThread()) in the DefaultISMLocking we must
call it on every instance of the
DefaultISMLocking with maybe a observation pattern ?
What do you think ?


> Deadlock with XA enabled
> ------------------------
>                 Key: JCR-1334
>                 URL: https://issues.apache.org/jira/browse/JCR-1334
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, jackrabbit-jca
>    Affects Versions: 1.4
>         Environment: WebSphere Application Server 5.1
>            Reporter: Claus Köll
>            Priority: Critical
>         Attachments: javacore.20080121.132210.2524.txt, lock_output.txt, PatchedDefaultISMLocking.java,
PatchedDefaultISMLocking_2.java, Stacktrace.txt
> Since we have configured a j2c resource adapter any modification to the repository ends
> with a deadlock.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message