[
https://issues.apache.org/jira/browse/JCR-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1940.
--------------------------------
Resolution: Invalid
Re-resolving as Invalid.
Alexander's concern about a potential clustering issue would only have been
valid if your non-clustered configuration would have been correct. As it
stands, you're seeing normal Jackrabbit behaviour described by Alexander.
Please contact the [email protected] list for more background on why
Jackrabbit does this, and for ways to avoid such issues. The issue tracker is
only for cases where changes to Jackrabbit behaviour is needed.
> 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
>
> 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.
