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

rsauer edited comment on JCR-1334 at 9/15/08 5:16 AM:
------------------------------------------------------------

Hi,

I got the same issue on Tomcat with Jencks when using ...rmi.ClientXASession. The prepare and commit requests seem to arrive sometimes at different threads, causing a deadlock.

I understand that RMI gives no guarantee on which thread requests are served, so I fully agree that locking should not be thread based.

Btw., I tested with the attached PatchedDefaultISMLocking class and I still get errors, although no deadlocks. I get a stale item state exception on commit after deleting a node having versions. So this does not seem to be a solution currently.

Robert

      was (Author: rsauer):
    Hi,

I got the same issue on Tomcat with Jencks when using ...rmi.ClientXASession. The prepare and commit requests seem to arrive sometimes at different threads, causing a deadlock.

I understand that RMI gives no guarantee on which thread requests are served, so I fully agree that locking should not be thread based.

Btw., I tested with teh attached {{PatchedDefaultISMLocking}} class and I still get errors, although no deadlocks. I get a stale item state exception on commit after deleting a node having versions.

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