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, 25 Feb 2008 15:04:51 GMT

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

Claus Köll commented on JCR-1334:
---------------------------------

hi marcel,
no i don't perform versioning operations.
i only try to add a node. and this is the only operation where the deadlock occurs.
please read my comment from 13/Feb/08 09:48 AM,
there i have hopefully eyplained the deadlock, hope you can follow me :-)

The active writer will be changed in the DefaultISMLocking-Instance of the SharedItemStateManager.
The allowReader comes from the DefaultISMLocking-Instance hold by the VersionItemStateProvider
and
in this Instance is the wrong Thread set.

thanks lot
claus


> 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.


Mime
View raw message