[
https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800163#action_12800163
]
Thomas Mueller commented on JCR-2456:
-------------------------------------
Hi Bart
Those exceptions are expected currently. I tlooks like you set IGNORE_ERRORS to
false (right?), otherwise you shouldn't see the stack traces (you should only
see one line per exception).
The 'real' problem (what this bug is about) is that even after restarting the
repository, a node can no longer be deleted. That means the persisted state
(the data stored in the persistence manager) of the repository is corrupt: a
node refers to a child node that doesn't exist.
I suggest to reset IGNORE_ERRORS (to true) and let the test case run until it's
finished (it will take a few minutes). If you don't see a stack trace then
everything is fine.
> Repository is corrupt after concurrent changes with the same session
> --------------------------------------------------------------------
>
> Key: JCR-2456
> URL: https://issues.apache.org/jira/browse/JCR-2456
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.0-beta4
> Reporter: Thomas Mueller
> Attachments: patch-2456.txt, TestMultiThread.java
>
>
> After concurrent write operations using the same session, the repository can
> get corrupt, meaning a ItemNotFoundException is thrown when trying to remove
> a node.
> Concurrent write operations are not supported, however I believe the
> persistent state of the repository should not be get corrupt.
> One way to solve this problem is to synchronize on the session internally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
