You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Robert Sauer (JIRA)" <ji...@apache.org> on 2008/09/15 12:45:44 UTC
[jira] Issue Comment Edited: (JCR-1334) Deadlock with XA enabled
[ 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 3:43 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.
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.
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.