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, 13 Feb 2008 17:49:08 GMT

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

Claus Köll commented on JCR-1334:

hi marcel,
is it possible that the are running two instances of the DefaultISMLocking Object ?
As i can see there will be generated a instance in the WorkspaceInfo.doInitalize() Method
and one in the RepositoryImpl.createVersionManager() Method.
I think on the downgrade Method the active Thread will be set coming from the SharedItemStateManager
hold by the Workspace
and the deadlock call comes from the VersionItemStateProvider.hasItemState and this call goes
to the DefaultISMLocking Object that holds
the wrong active Thread.
i hope i have explained it that you can follow me ;-)

> 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