jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1334) Deadlock with XA enabled
Date Fri, 18 Apr 2008 12:38:22 GMT

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

Marcel Reutegger commented on JCR-1334:

Hi Claus,

that's good news. however be warned, that there still might be an issue. I ran our daily integration
test with the patched DefaultISMLocking class and some tests failed with an exception.

I'll have to further investigate what causes those errors, but once those are resolved I'll
commit the changes.

> 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.

View raw message