[
https://issues.apache.org/jira/browse/JCR-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889823#action_12889823
]
Laurent Prevosto commented on JCR-2679:
---------------------------------------
We were aware of JCR-2554. that's why we moved from 1.5.3 to 1.6.2 but the
problem remained.
FineGrainedISMLockinf is present in both repository.xml and workspace.xml and
(see attachments)
Regarding Sessions : a spring bean opens a session for every method of the bean
and closes it in a finally clause. So sessions are not shared across multiple
threads. But it is possible to open & close several sessions in a given
transaction.
We are also experimenting the following scheme (probably better anyway) :
We use the JCR spring module : spring is reponsible for opening and closing the
session and there is only one session per transaction. But it looks like we
managed to have the deadlock occur.
> Lock Problem when accessing JCR
> -------------------------------
>
> Key: JCR-2679
> URL: https://issues.apache.org/jira/browse/JCR-2679
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 1.5.3, 1.6.2
> Environment: JBOSS 4.2.3 on jre 1.5.0_15 with XA transactions and
> Oracle10g
> Reporter: Laurent Prevosto
> Priority: Critical
> Attachments: thread_dump.txt
>
>
> Hi,
> We're using Jackrabbit 1.6.2 as an internal CMS in an application we
> developped.
> It runs in JBOSS 4.2.3 on jre 1.5.0_15 with XA transactions and Oracle10g
> We have about 15 users adding / deleting files in the repository.
> 30 others just do read only CMS access and other stuff.
> Things work fine except that sometimes, suddenly everything gets stuck and
> all we have left is those kind of errors :
> [org.apache.jackrabbit.core.query.lucene.NodeIteratorImpl] : Exception
> retrieving Node with UUID : XXXXXXX-XXX-etc: javax.jcr.ItemNotFoundException:
> XXXXXXX-XXX-etc
> All our JCR connections are now dead. If we restart JBOSS, things get back to
> normal, until the next crash.
> It looks like the bug usually happens when this kind of sequence takes place
> (though that may not be the only one) :
> XA transaction begins
> filenode1 gets deleted
> filenode2 gets deleted
> other oracle stuff takes place... and fails
> XA rollbacks.
> => JCR is dead.
> At that point, "touching" the datasource has it reinitialised by JBOSS but
> unfortunately the lock is still there : JBOSS has to be restarted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
