Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <23718854.1202377628233.JavaMail.jira@brutus>
Date: Thu, 7 Feb 2008 01:47:08 -0800 (PST)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-1334) Deadlock with XA enabled
In-Reply-To: <3651182.1200922415389.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-1334?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D125665=
24#action_12566524 ]=20

Claus K=C3=B6ll 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=
=20
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=C3=B6ll
>            Priority: Critical
>         Attachments: javacore.20080121.132210.2524.txt, lock_output.txt
>
>
> Since we have configured a j2c resource adapter any modification to the r=
epository ends
> with a deadlock.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.