[ https://issues.apache.org/jira/browse/JCR-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576914#action_12576914
]
Marcel Reutegger commented on JCR-1334:
---------------------------------------
The second locking object belongs to the version storage. If that lock has a active writer
then your code uses versioning. Is one of your nodes mix:versionable?
Did you also configure the ISMLocking in the repository.xml for version storage as well?
> 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.
|