[
https://issues.apache.org/jira/browse/JCR-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568575#action_12568575
]
Marcel Reutegger commented on JCR-1334:
---------------------------------------
> when will the downgrade be called ?
downgrade is called in SharedItemStateManager.Update.end()
> because the deadlock comes from the searchmanager. he calls
> DefaultISMLocking.acquireReadLock and this
> call comes from a different thread than from downgrade.
no, I don't think so. the stacktrace includes the Update.end() call and at the
time EventStateCollection.dispatch() is called the lock is downgraded and
associated with the current thread that later calls acquireReadLock().
> 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.
