[
https://issues.apache.org/jira/browse/JCR-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541362
]
Stefan Guggisberg commented on JCR-1197:
----------------------------------------
my 2 cents:
i don't believe that this issue is related to ItemManager's cache of ItemImpl
instances.
<quote from ItemManager's javadoc>
The ItemManager's responsabilities are:
...
guaranteeing that there aren't multiple instances representing the same Node or
Property associated with the same Session instance.
...
</quote from ItemManager's javadoc>
there's no need to explicitly evict cached ItemImpl instances from
ItemManager's cache.
quite the contrary, doing so would violate the ItemManager's contract.
> ItemManager cache is getting out of sync
> ----------------------------------------
>
> Key: JCR-1197
> URL: https://issues.apache.org/jira/browse/JCR-1197
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.3.3, 1.4
> Reporter: Przemo Pakulski
> Priority: Critical
> Fix For: 1.4
>
> Attachments: CheckoutFailure.java
>
>
> It seems that ItemManager cache is not maintained correctly. I'm getting
> InvalidItemStateException: 'propertyId' has been modified externally tryin
> restore/checkout versionable nodes in single thread.
> ItemState should be evicted from ItemStateManager cache when modified, it
> seems that status of ItemState is changed to MODIFIED, but itemState remains
> in the cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
