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] Commented: (JCR-1334) Deadlock with XA enabled
Date Wed, 16 Apr 2008 05:10:24 GMT

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

Claus Köll commented on JCR-1334:
---------------------------------

hi marcel,
yesterday i have tested again to find a solution for that issue and i have taken the newest
packages (core, common and rmi) and i don't know why but your pactch works now fine.
the VersionItemStateprovider.hasItemState will not be called anymore so no deadlock occurs.
from my side it would be great if you can apply your patch to the trunk.
it will work till we dont use versionable nodes but this is no requirement for us ..

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


Mime
View raw message