[
https://issues.apache.org/jira/browse/JCR-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1940.
--------------------------------
Resolution: Invalid
Assignee: Jukka Zitting
As I said, please use the [email protected] mailing list instead of
reopening this issue.
There are well defined ways in JCR for avoiding this issue. JCR-584 (available
since Jackrabbit 1.2) is one, separate subtrees is another, and the JCR locking
feature yet another.
Clustering makes this issue somewhat more prominent, but see JCR-1753 for a
proposed mechanism to better deal with the clustering delay.
The current consensus is that these "has been modified externally" exceptions
are perfectly acceptable. And as mentioned by Alexander, they are also
explicitly allowed by the JCR specification. You're of course welcome to
challenge this consensus, but I'd propose that you rather do that on the
[email protected] mailing list and follow up with an improvement issue
once there's a clearer idea of what you'd like to change.
> Exception when concurrently adding documents to Jack rabbit repository with
> clustering enabled
> ----------------------------------------------------------------------------------------------
>
> Key: JCR-1940
> URL: https://issues.apache.org/jira/browse/JCR-1940
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: OS - Win 2000
> JackRabbit Jars - 1.5
> Reporter: Richa Khurana
> Assignee: Jukka Zitting
>
> We have a enabled jackrabbit clustering. In this mode following exception
> occurs when 2 users simultaneouly add documents to Jack rabbit repository
> registered with node id 1 and 2 respectively-
> 14:59:55,312 ERROR [DocumentHelper] Exception occurred while adding a
> manually uploaded document to the jackrabbit:
> javax.jcr.InvalidItemStateException: cafebabe-cafe-babe-cafe-babecafebabe has
> been modified externally
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1109)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:846)
> Another observation is that when we disable clustering and both users have
> same node id in cluster configuration in repository.xml, the error doesnt
> appear.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
