jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hugo Lassiège (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2679) Lock Problem when accessing JCR
Date Wed, 04 Aug 2010 08:48:19 GMT

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

Hugo Lassiège commented on JCR-2679:

For information, I reuse the ConcurrentNodeModificationTest available in jackrabbit-tests
to test the JCR against multiple node creation/deletion. 

I met problems with and without the FineGrainedISMLocking. 

04 août 2010 09:58:02,688 ERROR ConcurrentNodeModificationTest: Operation failed
javax.jcr.InvalidItemStateException: Item cannot be saved because it has been modified externally:
node /
	at org.apache.jackrabbit.core.ItemImpl.getTransientStates(ItemImpl.java:245)
	at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:939)
	at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
	at com.sfr.thd.sadirah.test.jackrabbit.ConcurrentNodeModificationTest$TestSession.runIteration(ConcurrentNodeModificationTest.java:109)
	at com.sfr.thd.sadirah.test.jackrabbit.ConcurrentNodeModificationTest$TestSession.run(ConcurrentNodeModificationTest.java:84)
	at java.lang.Thread.run(Thread.java:595)

(However this is not the same context as I'm not in a XA transaction. )

> 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: repository-prod.xml, thread_dump.txt, workspace.xml
> 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.

View raw message