Potential concurrency issues of Workspace operations
----------------------------------------------------
Key: JCR-2290
URL: https://issues.apache.org/jira/browse/JCR-2290
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Reporter: Stefan Guggisberg
while investigating JCR-2269 i discovered that the following
javax.jcr.Workspace operations are affected by potential concurency issues:
copy
clone
move
importXML
getImportContentHandler
those operations directly operate on ItemState instances returned from
LocalItemStateManager (LISM).
typically a workspace operation gets an ItemState instance from the LISM, does
some validations,
modifies the state and finally stores it in the ChangeLog for further
processing.
the problem is that the local ItemState instance is not isolated from external
changes, i.e. it might change
at any point (e.g. after validation) due to external underlying changes. only
when it is stored in the
ChangeLog it is disconnected from its underlying state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
