[
https://issues.apache.org/jira/browse/JCR-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569813#action_12569813
]
Claus Köll commented on JCR-1334:
---------------------------------
as i mentioned before with the two instances, i think this is the problem
this is the call stack:
DefaultISMLocking.acquireWriteLock(), CurrentThreadName: ORB.thread.pool : 2
DefaultISMLocking.acquireWriteLock().downgrade(), CurrentThreadName:
ORB.thread.pool : 0
DefaultISMLocking.RWLock().setActiveWriter(ORB.thread.pool : 0), Instance:
[EMAIL PROTECTED], CurrentThreadName: ORB.thread.pool : 0
***** Different Thread access
***** Hold Thread in RWLock: ORB.thread.pool : 2
***** givenThread :ORB.thread.pool : 0
...
DefaultISMLocking.RWLock().allowReader() activeWriter: ORB.thread.pool : 2,
Instance: [EMAIL PROTECTED], CurrentThreadName: ORB.thread.pool : 0
the downgrade is called on a other instance of the RWLock,
then the allowReader comes from a other thread an the hold activeWriter Thread
in the RWLock is a different one.
i don't know why there are two instances of the DefaultISMLocking Object.
> 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.
