[
https://issues.apache.org/jira/browse/JCR-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561973#action_12561973
]
Claus Köll commented on JCR-1334:
---------------------------------
what do you think about
to bind the locks not to a thread but rather to the transactioncontext if we
run in a xa environment,
because you can not guarantee that the prepare and commit comes from the same
thread in a container managed transaction
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.
