jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1334) Deadlock due different Thread access while prepare and commit in same Transaction
Date Wed, 11 Feb 2009 13:13:00 GMT

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

Jukka Zitting updated JCR-1334:
-------------------------------

    Fix Version/s:     (was: 1.6.0)
                   1.5.3

Good stuff! Merged to the 1.5 branch in revision 743318.

> Deadlock due different Thread access while prepare and commit in same Transaction
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-1334
>                 URL: https://issues.apache.org/jira/browse/JCR-1334
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.4
>         Environment: WebSphere Application Server 5.1
>            Reporter: Claus Köll
>            Assignee: Claus Köll
>            Priority: Critical
>             Fix For: 1.5.3
>
>         Attachments: javacore.20080121.132210.2524.txt, lock_output.txt, PatchedDefaultISMLocking.java,
PatchedDefaultISMLocking_2.java, Stacktrace.txt, xa_patch.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.


Mime
View raw message