[jira] Commented: (JCR-1334) Deadlock with XA enabled

["Claus Köll (JIRA)" <ji...@apache.org>]

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

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

hi guys,
what do others think ?
i think we can not per default bind a lock to a thread. this will work good for a standalone server
but not in a xa environment with container transactions on a j2ee server
we run now for about a half year with jackrabbit in production but without 
xa transactions and this is no good solution
hope somebody will help to solve that problem
br
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
>
>
> 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.