jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Köll (JIRA) <j...@apache.org>
Subject [jira] Updated: (JCR-1334) Deadlock with XA enabled
Date Mon, 22 Sep 2008 08:14:44 GMT

     [ https://issues.apache.org/jira/browse/JCR-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Claus Köll updated JCR-1334:

    Attachment: xa_locking.patch

I have implemented a extension to the current Locking Strategy that binds the lock to thread.

Now the lock will not only be bound to the thread but also bound with the Xid to a ThreadLocal
Object for the current transaction
This patch implements also the code for JCR-1702 patch

> 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, xa_locking.patch
> 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.

View raw message