[
https://issues.apache.org/jira/browse/JCR-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905001#action_12905001
]
Claus Köll commented on JCR-2679:
---------------------------------
Hi,
>We are quite reluctant to use normal jdbc connection as we need to use the
>transactionnal XA datasource provided by Jboss.
Jackrabbit must not use a transactional XA DataSource taht is part of the XA
Transaction for its DB Connection.
The DataSource must not be involved in the XA Transaction because Jackrabbit
itself is the XA Resource.
So please test with a normal jdbc connection in your repository/workspace.xml
file.
greets
claus
> Lock Problem when accessing JCR
> -------------------------------
>
> Key: JCR-2679
> URL: https://issues.apache.org/jira/browse/JCR-2679
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jca, transactions
> 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
> 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.
